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

Difference between revisions of "ICE Build Instructions"

 
(38 intermediate revisions by 7 users not shown)
Line 1: Line 1:
ICE is relatively easy to build from scratch if you know where to start. This article assumes that you have already collected the ICE Third Party Dependencies and have them in your workspace or stored on your system. Information on obtaining those dependencies will not be provided here until the IP review is complete.
+
'''We now recommend that all ICE developers hack the code from ICE itself. See [[Getting ICE]] to download it.  
 +
'''
  
== Tooling ==
+
This article assumes that you have already collected the [[Getting_ICE#Prerequisites|ICE third-party dependencies]] and have them in your workspace or stored on your system. All third-party dependencies are required to build ICE from source, unlike the binary distribution of ICE.  Additional dependencies may be required to use certain features of ICE.
  
Building ICE will work out of the box with Eclipse Luna since it has both the EGit and M2E (Maven) plugins installed by default. You may have to install these plugins manually if you are using an older version of Eclipse.
+
''Building ICE from scratch requires access to some test files for its tests to pass. You can either build it without the tests by disabling them with Maven or you can check the tests out from https://github.com/jayjaybillings/ICETests. You should clone the tests directly into your home directory using the following command if you are using a shell:''
 +
 
 +
<pre>
 +
git clone https://github.com/jayjaybillings/ICETests
 +
</pre>
 +
 
 +
ICE requires Java 1.8 to build and run.
  
 
== Getting ICE from Git ==
 
== Getting ICE from Git ==
  
The first step is checking ICE out from its Git repository. The preferred way to do this is to use Eclipse and clone the Git repo. The Git repository is at [http://github.com/eclipse/ice]. Using the Eclipse Git tooling makes it exceptionally easy to checkout the projects.
+
The first step will be to check ICE out from the Git repository. If you are building ICE using ICE, check it out from Developer > ICE > Clone ICE from the menu bar. If you are using another version of Eclipse you can do it manually. The Git repository is at http://github.com/eclipse/ice.  
 +
 
 +
Open the Git Repositories view (Window > Show View > Other... Expand Git and select Git Repositories.) and choose to clone a repository. Point the wizard to the ICE Git repository, and click Next. The ICE Git repository needs to be cloned into your workspace so that it can run its build properly. If your workspace is at <code>$HOME/workspace</code>, the repository should be cloned into <code>$HOME/workspace/ice</code> as shown in the second picture.
 +
 
 +
'''Be sure to check the box''' that says "Import all existing projects after clone is finished." Selecting this option will automatically import all Eclipse ICE projects into your workspace and save you quite a bit of time by preventing you from having to learn how the repository is organized.
 +
 
 +
[[File:ICEGithubConfig.png]] [[File:ICEGithubLocConfig.png]]
 +
 
 +
If you are using a vanilla version of Eclipse for development, all of the projects will show up in your Project Explorer, and most of them will have red error boxes next to them. You will need to load the target platform by opening the org.eclipse.ice.target.mars project, opening the "mars.target" file, and clicking the "Set as target platform" button in the top right of the editor once the platform has resolved. Resolving the platform takes a very long time if you have never done it before, so watch the status bar in the bottom right to monitor its progress.
 +
 
 +
If you are using ICE to do ICE development, you do not need to resolve the target platform unless you need to make changes to it.
  
 
== Building ICE Binaries using Maven ==
 
== Building ICE Binaries using Maven ==
  
ICE is built using the [Maven build system](http://maven.apache.org/). ICE utilizes the Maven build system for creating binaries for multiple platforms and architectures as well as executing the test plugins. The Maven build system can be launched by command line using the mvn command or from within Eclipse using the m2e Eclipse plugin. Screenshots for this section are available at the end.  
+
ICE is built using the [http://maven.apache.org/ Maven build system] and [https://www.eclipse.org/tycho/ Eclipse Tycho] to create binaries for multiple platforms and architectures and to execute the test plugins. The Maven build system can be launched by command line using the <code>mvn</code> command, if it is installed, or from within Eclipse using the m2e Eclipse plugin.
 +
 
 +
ICE is a big code, so properly building for the first time can be a lengthy process because ICE's dependencies need to be downloaded.
 +
 
 +
'''Make sure that you are in the 'next' branch.''' This should be done automatically if you used the Developer Menu, but if you have [ice master] next to your package names inside Eclipse, then do ''Window -> Show View -> Other'' and select ''Git''. Then right click the ice repository and select ''Switch To... -> New Branch'' and select ''next'' as the source.
 +
 
 +
In practice, if you are doing development work and don't need to build the binaries, you can just build the bundles and run the tests. It is good practice to build the binaries and run them at least once a day to make sure your code works in the way the user will experience it.
 +
 
 +
The ICE Development Team builds ICE from both the command line and Eclipse: we build from inside Eclipse while we are developing and before we commit to make sure the tests work, and we use an automated Hudson build that runs hourly on our development server.
 +
 
 +
To build ICE on the command line, change into the org.eclipse.ice.aggregator directory and run
 +
<pre>
 +
mvn clean verify
 +
</pre>
 +
 
 +
The binaries will be in ice/org.eclipse.ice.repository/target/products within your ICE working copy.
 +
 
 +
=== Inside Eclipse ===
 +
 
 +
In order to build ICE binaries from Eclipse, you must use the [http://www.eclipse.org/m2e/|m2e Eclipse plugin for Maven]. Once the ICE plugins are checked out from the repository, make sure you can see packages in the Package Explorer. If not, you may not have checked the "Import all existing projects after clone is finished" box when cloning ICE.  You can import the projects from the Git perspective by right-clicking on the ICE repository and selecting "Import Projects".
 +
 
 +
'''Build and Test the ICE Bundles'''
 +
 
 +
You can build and test ICE by simply selecting ''Developer -> ICE -> build''. For better control over the build process, we can create a custom run configuration. Look for <tt>pom.xml</tt> in the <code>org.eclipse.ice.aggregator/</code> directory.
 +
 
 +
[[File:FindPOM.png]]
 +
 
 +
Right-click this file, and select 'Run As... > Run Configurations' near the bottom of the context menu. In the dialog that appears, select the 'Maven Build' option in the left-side menu, and click the new button (a small button that looks like a blank piece of paper with a gold plus sign on it) near the upper left of the dialog. A new configuration will be created. You need to set the name at the top of the page, choose the <code>org.eclipse.ice.aggregatory/</code> directory by clicking the "Browse Workspace" button and set the goal to <code>clean verify</code> to properly launch the build. Click 'Apply' and then 'Run.'
 +
 
 +
[[File:Ice_build_20160211.png]]
  
#### On the Command Line
+
If the build system encounters any errors or failed tests, they will be reported in the Eclipse console window, and the build will be terminated early. Alternatively, if the build is successful, a "BUILD SUCCESS" message will be displayed in the console once the build completes, and the ICE binaries will have been created in your Eclipse workspace at org.eclipse.ice.repository/target/products. If you experience any issues with the build send your error logs to <code>ice-dev <at> eclipse.org</code>.
  
Once Maven is installed, open a terminal window and change your current directory to the org.eclipse.ice.build/eclipse directory within your ICE Eclipse workspace (the default directory where you told Eclipse to install your files). Next, execute the following two statements in order:
+
The org.eclipse.ice.repository/target/products directory contains a p2 repository; compressed (ZIP) files of ICE for 32- and 64-bit Linux, Mac, and Windows; and unzipped directories with the executables for each platform that can be immediately executed.
   
+
    mvn -N install
+
    mvn install
+
  
The first command downloads and installs the required dependencies, which may take several minutes to complete, and it installs the ICE "parent" build configuration in your local Maven repository. The second command builds the ICE source and test bundles, executes the tests, and creates binaries if the tests pass. This may take a very long time if it is the first time you are building ICE, because Maven will download a lot of other plugins that it needs to build Eclipse RCP applications and to bootstrap itself. However, subsequent builds take about four minutes.
+
A successful build looks like the following:
  
If you don't want to build ICE from files stored within your Eclipse workspace or if you downloaded the entire trunk directory from the repository, you can still build ICE. There is a second Maven build script located in trunk/src/org.eclipse.ice.build/hudson that is set up to build with the default trunk configuration. You can use the same commands to build with this script, and it should produce the same results. The ICE Dev Team uses both: we build from inside Eclipse while we are developing and before we commit to make sure the tests work, and we use the second script with an automated Hudson build that runs hourly on our development server.  
+
[[File:Ice_build_console_20160210.png]]
  
### Inside Eclipse
+
== Updating version numbers ==
  
In order to build ICE binaries from Eclipse, you must use the [m2e Eclipse plugin for Maven](http://www.eclipse.org/m2e/). It is recommended that the slf4j optional plugin be installed as well. Once the plugins are installed, open the org.eclipse.ice.build package and go to the eclipse directory. We need to follow the same steps as listed above, but in Eclipse there is no way to just execute a command like mvn -N install.
+
Maven can be used to update the release version number in ICE for MANIFEST.mf and pom.xml files, with two exceptions. From the command line, execute the Tycho Versions plugin as follows:
 +
<pre>
 +
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.2.1-SNAPSHOT -Dtycho.mode=maven -Dartifacts=org.eclipse.ice.parent
 +
</pre>
  
Since we have to run this command to install our parent build configuration, we need to create a custom run configuration. Right-click on the pom.xml file, scroll to _Run As..._ and select _Run Configurations_ at the bottom. In the menu that appears, select the _Maven Build_ option in the left-side menu and click the new button (a small button that looks like a blank piece of paper with a gold plus sign on it) at the top. A new configuration will be created. You need to set the name at the top of the page, choose the org.eclipse.ice.build/eclipse directory and set the goal to -N install to properly launch the build. Click _Apply_ and then _Run_.  
+
In org.eclipse.ice.parent/pom.xml, change the version of the target in the block below
 +
<pre>
 +
<target>
 +
    <artifact>
 +
        <groupId>org.eclipse.ice</groupId>
 +
        <artifactId>org.eclipse.ice.target.oxygen</artifactId>
 +
        <version>2.2.1-SNAPSHOT</version>
 +
        <classifier>oxygen</classifier>
 +
    </artifact>
 +
</target>
 +
</pre>
  
This downloads and installs any required dependencies, and will probably take a while if this is your first time building ICE binaries. Once all dependencies are downloaded, the last step is to actually build ICE. To do this, right-click on the same pom.xml file in the org.eclipse.ice.build/eclipse directory, and select _Run As_ &gt; _Maven install_. This will build and test all of ICE's bundles. If this is your first time, this process could take upwards of 10-12 minutes depending on your system. If the build system encounters any errors or failed tests, they will be reported in the Eclipse console window, and the build will be terminated early. Alternatively, if the build is successful, a "BUILD SUCCESS" message will be displayed in the console once the build completes, and the ICE binaries will have been created in your Eclipse workspace.  
+
to the desired version number. Finally, in the same file, change the release name tag on line 7 to the new value as shown below
 +
<pre>
 +
<releaseName>2.2.1RC3</releaseName>
 +
</pre>
  
### Locating the ICE Binaries
+
== Tips ==
  
The resulting ICE binaries are written to a subdirectory of the org.eclipse.ice.repository package under target/products. Note that the target directory may not appear in the Eclipse Package Explorer until the org.eclipse.ice.repository package has been refreshed. To refresh this package, right-click on the package and select _Refresh_. To execute a resulting binary, unzip the product for your platform and architecture, go into the ICE directory, and run the _ICE_ executable.
+
==== Building on Arch Linux ====
 +
To build ICE on Arch Linux with <tt>openjdk</tt> it is necessary to install the <tt>java-openjfx</tt> package from [https://www.archlinux.org/packages/extra/i686/java-openjfx/| the official repositories].

Latest revision as of 22:32, 5 May 2017

We now recommend that all ICE developers hack the code from ICE itself. See Getting ICE to download it.

This article assumes that you have already collected the ICE third-party dependencies and have them in your workspace or stored on your system. All third-party dependencies are required to build ICE from source, unlike the binary distribution of ICE. Additional dependencies may be required to use certain features of ICE.

Building ICE from scratch requires access to some test files for its tests to pass. You can either build it without the tests by disabling them with Maven or you can check the tests out from https://github.com/jayjaybillings/ICETests. You should clone the tests directly into your home directory using the following command if you are using a shell:

git clone https://github.com/jayjaybillings/ICETests

ICE requires Java 1.8 to build and run.

Getting ICE from Git

The first step will be to check ICE out from the Git repository. If you are building ICE using ICE, check it out from Developer > ICE > Clone ICE from the menu bar. If you are using another version of Eclipse you can do it manually. The Git repository is at http://github.com/eclipse/ice.

Open the Git Repositories view (Window > Show View > Other... Expand Git and select Git Repositories.) and choose to clone a repository. Point the wizard to the ICE Git repository, and click Next. The ICE Git repository needs to be cloned into your workspace so that it can run its build properly. If your workspace is at $HOME/workspace, the repository should be cloned into $HOME/workspace/ice as shown in the second picture.

Be sure to check the box that says "Import all existing projects after clone is finished." Selecting this option will automatically import all Eclipse ICE projects into your workspace and save you quite a bit of time by preventing you from having to learn how the repository is organized.

ICEGithubConfig.png ICEGithubLocConfig.png

If you are using a vanilla version of Eclipse for development, all of the projects will show up in your Project Explorer, and most of them will have red error boxes next to them. You will need to load the target platform by opening the org.eclipse.ice.target.mars project, opening the "mars.target" file, and clicking the "Set as target platform" button in the top right of the editor once the platform has resolved. Resolving the platform takes a very long time if you have never done it before, so watch the status bar in the bottom right to monitor its progress.

If you are using ICE to do ICE development, you do not need to resolve the target platform unless you need to make changes to it.

Building ICE Binaries using Maven

ICE is built using the Maven build system and Eclipse Tycho to create binaries for multiple platforms and architectures and to execute the test plugins. The Maven build system can be launched by command line using the mvn command, if it is installed, or from within Eclipse using the m2e Eclipse plugin.

ICE is a big code, so properly building for the first time can be a lengthy process because ICE's dependencies need to be downloaded.

Make sure that you are in the 'next' branch. This should be done automatically if you used the Developer Menu, but if you have [ice master] next to your package names inside Eclipse, then do Window -> Show View -> Other and select Git. Then right click the ice repository and select Switch To... -> New Branch and select next as the source.

In practice, if you are doing development work and don't need to build the binaries, you can just build the bundles and run the tests. It is good practice to build the binaries and run them at least once a day to make sure your code works in the way the user will experience it.

The ICE Development Team builds ICE from both the command line and Eclipse: we build from inside Eclipse while we are developing and before we commit to make sure the tests work, and we use an automated Hudson build that runs hourly on our development server.

To build ICE on the command line, change into the org.eclipse.ice.aggregator directory and run

mvn clean verify

The binaries will be in ice/org.eclipse.ice.repository/target/products within your ICE working copy.

Inside Eclipse

In order to build ICE binaries from Eclipse, you must use the Eclipse plugin for Maven. Once the ICE plugins are checked out from the repository, make sure you can see packages in the Package Explorer. If not, you may not have checked the "Import all existing projects after clone is finished" box when cloning ICE. You can import the projects from the Git perspective by right-clicking on the ICE repository and selecting "Import Projects".

Build and Test the ICE Bundles

You can build and test ICE by simply selecting Developer -> ICE -> build. For better control over the build process, we can create a custom run configuration. Look for pom.xml in the org.eclipse.ice.aggregator/ directory.

FindPOM.png

Right-click this file, and select 'Run As... > Run Configurations' near the bottom of the context menu. In the dialog that appears, select the 'Maven Build' option in the left-side menu, and click the new button (a small button that looks like a blank piece of paper with a gold plus sign on it) near the upper left of the dialog. A new configuration will be created. You need to set the name at the top of the page, choose the org.eclipse.ice.aggregatory/ directory by clicking the "Browse Workspace" button and set the goal to clean verify to properly launch the build. Click 'Apply' and then 'Run.'

Ice build 20160211.png

If the build system encounters any errors or failed tests, they will be reported in the Eclipse console window, and the build will be terminated early. Alternatively, if the build is successful, a "BUILD SUCCESS" message will be displayed in the console once the build completes, and the ICE binaries will have been created in your Eclipse workspace at org.eclipse.ice.repository/target/products. If you experience any issues with the build send your error logs to ice-dev <at> eclipse.org.

The org.eclipse.ice.repository/target/products directory contains a p2 repository; compressed (ZIP) files of ICE for 32- and 64-bit Linux, Mac, and Windows; and unzipped directories with the executables for each platform that can be immediately executed.

A successful build looks like the following:

Ice build console 20160210.png

Updating version numbers

Maven can be used to update the release version number in ICE for MANIFEST.mf and pom.xml files, with two exceptions. From the command line, execute the Tycho Versions plugin as follows:

mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.2.1-SNAPSHOT -Dtycho.mode=maven -Dartifacts=org.eclipse.ice.parent

In org.eclipse.ice.parent/pom.xml, change the version of the target in the block below

<target>
    <artifact>
         <groupId>org.eclipse.ice</groupId>
         <artifactId>org.eclipse.ice.target.oxygen</artifactId>
         <version>2.2.1-SNAPSHOT</version>
         <classifier>oxygen</classifier>
    </artifact>
</target>

to the desired version number. Finally, in the same file, change the release name tag on line 7 to the new value as shown below

<releaseName>2.2.1RC3</releaseName>

Tips

Building on Arch Linux

To build ICE on Arch Linux with openjdk it is necessary to install the java-openjfx package from the official repositories.

Back to the top