Difference between revisions of "CBI/Eclipse Platform Build"

Revision as of 19:26, 12 January 2012

This page provides instructions for building the Eclipse Platform using preferred technologies identified as part of the CBI initiative.

At the moment, this build is a prototype based on a temporary fork of the Eclipse platform repositories. Access is not public yet, but if you'd like to try the build and provide feedback, please contact andrew dot ross at eclipse dot org to request.

Prerequisites

SUN Java 1.6

• SUN 1.6 JDK needs to be on PATH.
• Verify correct version of java is used

igor@desktop:~$ java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)

Maven 3.0.3

• Download from http://maven.apache.org/download.html
• Unpack to a local folder. On *nix, I usually unpack to /opt and create /opt/maven symlink so I can switch between different versions easily
• Do NOT use maven shipped with your linux distribution. Maven as shipped in Fedora 16 is perfectly capable of building the platform with the given instructions. Let's not generalize things and negate others work that easily!!!
• Verify correct maven version is used

igor@desktop:~$ mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: /opt/maven

"natives" p2 repository

This is a temporary workaround until we figure out how to build native binaries and bundles that wrap them

 mkdir -p /var/tmp/lts
 scp -r <userid>@build.eclipse.org:/home/data/users/cbi/natives \
   /var/tmp/lts/natives

Build environment setup

review maven settings.xml

To avoid getting hit by bug 365727 and to make sure your local environment configuration does not interfere with LTS build, make sure build user account does not have maven settings.xml

igor@desktop:~$ ls -l ~/.m2/settings.xml
ls: cannot access /home/igor/.m2/settings.xml: No such file or directory

give maven JVM more ram

 export MAVEN_OPTS=-Xmx512m

Eclipse 4.x Branch

cloning platform source tree

I setup single platform-aggregator git repository that references all required parts of the platform build is git submodules. The following command clones both the outer repository and all submodules

 git clone -b tycho-monolith-build --recurse-submodules \
  <userid>@dev.eclipse.org:/home/data/users/cbi/platform-aggregator.git R4_platform-aggregator

To update existing clone and all submodules

 git pull --recurse-submodules
 git submodule update

running the build

 mvn -f eclipse-parent/pom.xml \
   clean install \
   -Dmaven.repo.local=/var/tmp/lts/R4_localrepo

 mvn clean install \
   -Dmaven.repo.local=/var/tmp/lts/R4_localrepo -Dmaven.test.skip=true

With primed local repository, the build takes about 7 minutes on my 4+ years old linux desktop (core 2 duo @2.8GHz, SSD).

Packaged SDK zip files are located under

  TMP/org.eclipse.sdk.epp/target/products/

P2 repository

  TMP/org.eclipse.sdk.epp/target/repository

Eclipse 3.x Branch

cloning platform source tree

 git clone -b R3_tycho-monolith-build --recurse-submodules \
  <userid>@dev.eclipse.org:/home/data/users/cbi/platform-aggregator.git R3_platform-aggregator

To update existing clone and all submodules

 git pull --recurse-submodules
 git submodule update

running the build

 mvn -f eclipse-parent/pom.xml \
   clean install \
   -Dmaven.repo.local=/var/tmp/lts/R3_localrepo

 mvn -f maven-cbi-plugin/pom.xml \
   clean install \
   -Dmaven.repo.local=/var/tmp/lts/R3_localrepo

 mvn clean install \
   -Dmaven.repo.local=/var/tmp/lts/R3_localrepo -Dmaven.test.skip=true

Packaged SDK zip files are located under

  TMP/org.eclipse.sdk.epp/target/products/

P2 repository

 TMP/org.eclipse.sdk.epp/target/repository

Packaged JUnit Plugin Tests and Automated Testing Framework

 TMP/eclipse-junit-tests/target/eclipse-junit-tests-1.0.0-SNAPSHOT-bundle.zip