Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Common Build Infrastructure/Getting Started/Build In Eclipse

< Common Build Infrastructure‎ | Getting Started
Revision as of 14:22, 8 December 2009 by Nickboldt.gmail.com (Talk | contribs) (Required settings)

Warning2.png
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.


The process to run a build in Eclipse is getting ever easier.

Fetch workspace projects

  1. Download a .psf file, such as gef.psf
  2. Open Eclipse, and do File > Import > Team > Team Project Set. Browse for the .psf file you downloaded above, and import it. You should end up with three new workspace projects.
    1. org.eclipse.releng.basebuilder
    2. org.eclipse.dash.common.releng
    3. org.eclipse.gef.releng
  3. Download ant-contrib.jar 1.0b2 and put it into org.eclipse.dash.common.releng/lib/ant-contrib.jar.
Warning2.png
Ant Contrib 1.0b3
Ant Contrib 1.0b3 is not supported or recommended. Athena will download the correct jar if you tell it to in the build.properties file.


Configure build.properties

Open org.eclipse.gef.releng/build.properties and edit to suit your needs.

Required settings

The following properties must be set:

projectid=technology.foo
zipPrefix=MyFoo
version=0.5.0
buildType=N
mainFeatureToBuildID=org.eclipse.foo.all
testFeatureToBuildID=org.eclipse.foo.test
# if project is incubating, insert "-incubation" string into all generated zip file names; otherwise omit this 
incubation=-incubation
# set path and version of JVM to use; must set a variable for each Bundle-RequiredExecutionEnvironment (BREE) used in plugins
JAVA_HOME=/path/to/java/home
JAVA14_HOME=/path/to/java/home
JAVA50_HOME=/path/to/java/home
JAVA60_HOME=/path/to/java/home
dependencyURLs=http://download.eclipse.org/eclipse/downloads/drops/R-3.5.1-200909170800/eclipse-SDK-3.5.1-linux-gtk.tar.gz,http://path/to/other/required.zip
#what steps should we do? default: build.steps=buildUpdate,buildZips,buildTests,generateDigests,test,publish,cleanup
build.steps=buildUpdate,buildTests,generateDigests,testLocal,publish,cleanup

If you require SVN or do not have the test framework plugins in your map file, you will need this property too, or to perform the equivalent set up manually.

# To permit automatic downloads of non-EPL compatible code, set this to property to "I accept"
#thirdPartyDownloadLicenseAcceptance="I accept"

Optional settings

You can also set other PDE variables and compiler settings in your releng project's build.properties:

compilerArg=-enableJavadoc -encoding ISO-8859-1
flattenDependencies=true
parallelCompilation=true
generateFeatureVersionSuffix=true

Run a build

Select org.eclipse.gef.releng/build.xml, then Run As > Ant Build.

  • Ensure you have CVS installed on your machine.
  • If the compiler fails with errors like "Cannot find Object", make sure you have a JAVA_HOME for every BREE in your manifests. Please see the Common Build Infrastructure/Getting Started/FAQ.

A log of the build will appear as org.eclipse.gef.releng/buildlog.latest.txt.

  • If you receive errors related to test results not available, remove the "test" step from build.steps line.

Troubleshooting / server setup

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

Next Steps

Once you can build in Eclipse, you might want to get a job added to Hudson so you can run continuous integrations or nightlies, then start publishing to download.eclipse.org.

Back to the top