Jump to: navigation, search

Difference between revisions of "Libra/Getting Started"

m
m
Line 60: Line 60:
  
 
== Reproducing a Build to a Certain Change List ==
 
== Reproducing a Build to a Certain Change List ==
[http://wiki.eclipse.org/EGit/User_Guide#Fetching_a_change_from_a_Gerrit_Code_Review_Server Fetch to the specific change] and build with Maven as specified above.
+
[http://wiki.eclipse.org/EGit/User_Guide#Fetching_a_change_from_a_Gerrit_Code_Review_Server Fetch to the specific change] and build with Maven as described above.
  
 
= Send us feedback =
 
= Send us feedback =

Revision as of 13:03, 25 February 2011

Getting Started

Overview

The Libra project enables you to use tools that integrate the existing WTP tooling and PDE tooling so that OSGi Enterprise applications can be developed with both tooling at the same time. It also provides you with tools for better experience in the Server-Side Equinox scenario.

Installation and Use

Currently Libra supports only Eclipse Indigo. As a prerequisite you need to installEclipse IDE for Java EE Developers and Libra from this update site

The update site contains:

  • OSGi Facet Feature that introduces:
    1. A new facet "OSGi Bundle" for Dynamic Web, JPA and Utility projects.
    2. Wizard for converting WTP standard projects to OSGi Enterprise bundle projects:
      • Dynamic Web projects to Web Application Bundle projects
      • JPA projects to Persistent Bundle projects
      • Utility projects and simple Java projects to OSGi Bundle projects
Both options modify project's MANIFEST.MF in order to become a valid OSGi bundle.

The facet may be enabled during project creation or after that from Properties page of the project. The wizard is available from project's context menu Configure > Convert to OSGi Bundle Projects...

Note that you may need to adjust your target platform accordingly.

SCREENSHOT

Obtaining Sources

You can find the sources available in Git repository
In order to synchronize them locally, you may use EGit step-by-step procedure Screenshot

Builds

The build is based on Maven(at least 3.0.0) and Tycho, executed on Hudson server, hosted at Eclipse Foundation.

Maven Build Sequence

Complete build sequence for a clean build (assuming $M2_HOME/bin is on the path and local Maven repository at ~/.m2/repository):

[~/org.eclipse.libra/development/org.eclipse.libra.releng] $ mvn clean install
 Note that you may need to configure your proxy settings 

Proposing and Committing a Patch

"A patch is a piece of software designed to fix problems with, or update a computer program or its supporting data" (wikipedia). A patch file contains a description of changes of a set of resources which can be automatically applied to another eclipse workspace or git repository. If you want to propose or commit a patch you need to know that the Eclipse update hook will examine the Committer's entries of an incoming push. All the committer's entries have to be made by the committer performing the push, otherwise the push will fail. Furthermore, your committer ID, or the committer e-mail address registered with your committer account at the Eclipse Foundation must be present in the Committer Email record. For more information on that restriction see: this page.

Proposing a Patch

If you want commit a change on a local feature or bugfix branch and then to export this change into a patch file, follow the steps below:

  1. Open a bug
    • Specify the bug component (General; OSGi Facet or WAR)
    • Complete the fields about the product version, bug severity, type of your hardware, operating systems and write a summary and description of the patch
  2. Open the History view of your Eclipse IDE and choose Create Patch... (The patch file will contain the difference between the commit and its parent in the history view. Note that the filter of the history view applies also for patch creation.)
  3. Start the Patch Wizard, select the location of the patch and choose Next (The name of the patch file is created from the first line of the commit message.)
  4. Change the patch format, if necessary.
  5. Attach the patch created to the bug
  6. Submit the bug

Committing a Patch

To commit a patch, proceed as follows:

  1. Apply the proposed patch using the Patch Wizard
  2. Test the patch
  3. Commit the patch
  4. Setup push configuration with the following push URL:
    ssh://committer_id@git.eclipse.org/gitroot/libra/org.eclipse.libra.git
  5. Push the patch and see its change number in order to be able to inspect it

Reproducing a Build to a Certain Change List

Fetch to the specific change and build with Maven as described above.

Send us feedback

Mailing list

https://dev.eclipse.org/mailman/listinfo/libra-dev

Bugzilla

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Libra

Forum

http://www.eclipse.org/forums/eclipse.libra