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.
Difference between revisions of "Common Build Infrastructure/Getting Started/Build In Eclipse"
(→Troubleshooting / server setup) |
(→Run a build) |
||
Line 57: | Line 57: | ||
5. Select <code>org.eclipse.gef.releng/build.xml</code>, then <code>Run As > Ant Build</code>. | 5. Select <code>org.eclipse.gef.releng/build.xml</code>, then <code>Run As > Ant Build</code>. | ||
+ | * 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]]. | ||
6. A log of the build will appear as <code>org.eclipse.gef.releng/buildlog.latest.txt</code>. | 6. A log of the build will appear as <code>org.eclipse.gef.releng/buildlog.latest.txt</code>. |
Revision as of 01:35, 29 July 2009
The process to run a build in Eclipse is getting ever easier.
Contents
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.
org.eclipse.releng.basebuilder org.eclipse.dash.common.releng org.eclipse.gef.releng
3. Download ant-contrib.jar 1.0b2 (NOT 1.0b3!) and put it into org.eclipse.dash.common.releng/lib/ant-contrib.jar
.
Configure build.properties
4. 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=GEF 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 incubation=-incubation # if not incubating, set null string #incubation=
# set path and version of JVM to use; for 1.4, use JAVA14_HOME, for 6.0, use JAVA60_HOME JAVA_HOME=/opt/public/common/ibm-java2-ppc-50 JAVA50_HOME=/opt/public/common/ibm-java2-ppc-50 dependencyURLs=http://download.eclipse.org/eclipse/downloads/drops/S-3.5M6-200903130100/eclipse-SDK-3.5M6-linux-gtk-ppc.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,test,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
5. 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.
6. A log of the build will appear as org.eclipse.gef.releng/buildlog.latest.txt
.
Troubleshooting / server setup
If needs be, you may find additional information related to troubleshooting or server configuration here.