Jump to: navigation, search

Difference between revisions of "E4/Builds"

< E4
(Build Infrastructure)
(Build Infrastructure)
Line 29: Line 29:
 
The main build project is in e4/releng/org.eclipse.e4.builder.  We build using the start.sh script on build.eclipse.org.   
 
The main build project is in e4/releng/org.eclipse.e4.builder.  We build using the start.sh script on build.eclipse.org.   
  
We run the PDE builder using org.eclipse.e4.builder/builder/general as the ${builder} property, and usually build the org.eclipse.e4.master feature (which includes all the other features, tests, and examples).  Have a look at the arguments in the buildE4general launch config.
+
We run the PDE builder using org.eclipse.e4.builder/builder/general as the ${builder} property, and usually build the org.eclipse.e4.master feature (which includes all the other features, tests, and examples).  Have a look at the arguments in the buildE4general launch config.  To actually run this, you need to either have your machine set up like build.eclipse.org :-) or override a number of the path properties (JAVA14_HOME, JAVA15_HOME, etc).  See the org.eclipse.e4.builder/builder/general/build.properties for more information.
  
 
TODO:
 
TODO:

Revision as of 13:57, 20 November 2008

Builds

Integration Builds

E4 Integration Builds
Date Time Frequency
Thursdays 19:30 EST Weekly

e4 Downloads Page

Submitting For the Build

Teams should use the "Eclipse Releng Tools" to update their releng project for each build. The releng tools can be installed from the update sites already included in 3.5.

Tags: tags should be of the form v<date>, so v20081120 or v20081120-1300

Versioning Plugins: Teams should try and follow the standard versioning rules posted at Version_Numbering. If you need to copy over an existing eclipse project to make changes, please increment the minor number by 100. i.e. 3.5.0 becomes 3.105.0. When you need to break API, then update the major number. i.e. 3.105.0 becomes 4.0.0

Checking in code: The checkin comment should at a minimum include "bug #", and preferably be of the form "bug # summary"

Build Infrastructure

The main build project is in e4/releng/org.eclipse.e4.builder. We build using the start.sh script on build.eclipse.org.

We run the PDE builder using org.eclipse.e4.builder/builder/general as the ${builder} property, and usually build the org.eclipse.e4.master feature (which includes all the other features, tests, and examples). Have a look at the arguments in the buildE4general launch config. To actually run this, you need to either have your machine set up like build.eclipse.org :-) or override a number of the path properties (JAVA14_HOME, JAVA15_HOME, etc). See the org.eclipse.e4.builder/builder/general/build.properties for more information.

TODO:

  • sign the build.
  • generate a zip with 2 projects, org.eclipse.swt.e4 and org.eclispe.swt.e4.jcl, that can be imported into a workspace in an eclipse with the ActionScript tools installed.
  • Work with the Common_Build_Infrastructure to host our builds.
  • Teams need to generate source features
  • Figure out how to run tests
  • Send an email on sucess/fail

CVS

The resources, ui, and swt teams now have plugins in their team area in the e4 project. Our project is under :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse


Resources

The resources CVS structure is:

  • e4
    • org.eclipse.e4.resources
      • bundles
      • doc
      • examples
      • features
      • tests
    • releng
      • org.eclipse.e4.resources.releng

The org.eclipse.e4.resources.releng contains the map files for building as well as Team Project Sets that should be used for checking out the projects to be worked on.

Resources currently has 4 features. 2 feature patches for the plugins (one for rcp, one for platform), a feature that contains the 2 patches, and a test feature for the tests.

Setup/Restrictions

Resources can currently update a 3.5 SDK I build and run.

UI

The UI CVS structure is:

  • e4
    • org.eclipse.e4.ui
      • bundles
      • doc
      • examples
      • features
      • tests
    • releng
      • org.eclipse.e4.ui.releng

The org.eclipse.e4.ui.releng contains the map files for building as well as Team Project Sets that should be used for checking out the projects to be worked on.

UI currently has one main feature for the modelled workbench and one feature for the demos. The build master feature, org.eclipse.e4.master, is also in UI for now.

Setup/Restrictions

UI currently requires EMF 2.4.1 or 2.5.0 in installed on 3.5 in order to run. They can be installed from the update site included with the I builds.

SWT

The SWT CVS structure is:

  • e4
    • org.eclipse.e4.swt
      • bundles
      • doc
      • examples
      • features
      • tests
    • releng
      • org.eclipse.e4.swt.releng

The org.eclipse.e4.swt.releng contains the map files for building as well as Team Project Sets that should be used for checking out the projects to be worked on.

SWT has 2 features, one for the ActionScript tools and another for the ActionScript tests.

Setup/Restrictions

To update to the ActionScript tools you must first download and install the Open Source Flex SDK.

Setup Flex environment:

  1. Download and install the Adobe Open Source Flex SDK (available from http://opensource.adobe.com). NOTE: The path where you install the Flex SDK must contain no spaces. This is due to a bug in FCSH.
  2. update your eclipse.ini file and add another line at the end, -Dflex.sdk=<your path to the installed sdk>

Then you can update to the ActionScript tools. To work on the tools themselves, you must also set the FLEX_SDK classpath variable in Window>Preferences>Java>Build Path>Classpath Variables to point to the sdk location.


To work on org.eclipse.swt, org.eclipse.swt.e4.jcl, org.eclipse.swt.e4.examples, and org.eclipse.swt.examples you need to create a Linked Resource variable, WORKSPACE, that points to your current workspace root, from Window>Preferences>General>Workspace>Linked Resources. Also if .classpath_flex exists it must be copied to the .classpath entry.