* your.projects.name.here.releng (contains configurations and settings to drive PDE for building and testing)

−

The simplest way to get the first two projects is to download this [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.common.releng/psfs/athena.cvs.psf?revision=1.1&root=Technology_Project athena.cvs.psf].

+

====By Hand====

−

Next, open Eclipse, and do <code>File > Import > Team > Team Project Set</code>. Browse for the [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.common.releng/psfs/athena.cvs.psf?revision=1.1&root=Technology_Project athena.cvs.psf] file you downloaded above, and import it. You should end up with two new workspace projects.

Because the basebuilder project is used OUTSIDE of eclipse, it does not need to be open, or to have everything properly compiled, to function. In particular, due to licensing reasons, there is at least one jar (ie., j2ee.jar or javamail.jar) which is required to have everything in the project compile. This cannot be included in the project because it is not available under an EPL-compatible license.

+

* Close the <code>org.eclipse.releng.basebuilder</code> project to hide the compilation errors. These can be safely ignored.

−

The workaround is therefore to put the jar into the project by hand, or to simply close the project and ignore the compilation errors.

To fetch your project's releng folder, you will need to know where it is located in CVS or SVN. Some examples to try are at right:

+

To fetch your project's releng folder, you will need to know where it is located in CVS or SVN.

+

+

To create a new one, you can copy from the [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.myproject.releng/?root=Technology_Project sample project] then configure using the examples at right:

Note that some projects include a <code>psfs/</code> folder within their releng project to facilitate checking out sources, as in step 1 above.

Note that some projects include a <code>psfs/</code> folder within their releng project to facilitate checking out sources, as in step 1 above.

−

If you do not have a .releng project for your own code, you can create one based on the above examples.

+

=== Configure your .releng project ===

−

+

−

=== Configure build.properties ===

+

−

+

−

Open <code>your.project.releng/build.properties</code> and edit to suit your needs. There may be examples available for Windows, Linux, and MacOSX to help you get started. You can either copy from the .example file into build.properties, or point <code>build.xml</code> at the alternate build.properties.example.* file, like this:

# set path and version of JVM to use; must set a variable for
# each Bundle-RequiredExecutionEnvironment (BREE) used in plugins
# Or just use the default value provided by Eclipse, JAVA_HOME
JAVA14_HOME=${JAVA_HOME}
JAVA50_HOME=${JAVA_HOME}
JAVA60_HOME=${JAVA_HOME}

A log of the build will may appear as your.project.releng/buildlog.latest.txt, if you have configured a launch configuration to do so. Otherwise a complete buildlog.txt should appear in the destination folder where the build is created, eg., /tmp/build/N201001282334/buildlog.txt.

If you do not yet have tests available in your repository (or have not linked them from your map file(s), you may receive errors running the "test" or "testLocal" step.

Troubleshooting / server setup

If needs be, you may find additional information related to troubleshooting or server configuration here.