AF3 Product Distillery¶
Using the Maven/Tycho build environment already used on the Jenkins build server,
the product distillery allows to build the AF3 Phoenix Product on the local developer
Note that you are not allowed to publish your version of the AF3 product without
explicit permission of the AF3 development team. You are furthermore disallowed
to use or to change or to extend or to overwrite the AutoFOCUS 3 logo and/or the
product branding. You may propose your own branding as part of the permission process.
Setup the distillery environment¶
This page is composed of the folloing sections, corresponding merely to the steps which are necessary to transform the standard developer installation
into the product distillery environment installation:
- Check Java version to avoid Out-of-memory problems
- Setup a separate Eclipse and workspace installation
- Install the Maven Integration for Eclipse (m2e feature)
- Replace the fortiss-std-env with its distillery
- Check out additional Maven projects required to run the build
- Customize the product by adding Your own plugins to the build
- Create the product ZIP archives
- Custom Branding
1. Java version¶
This procedure has been confirmed to work with Java 8, but not
with Java 6. The behavior with Java 7 is currently untested and uncofirmed.
2. Separate Eclipse and workspace¶
The distillery procedure is to some extent destructive to Your
workspace and Eclipse installation.
It introduces the Maven extension and a replacement for the
fortiss-std-env. This also introduces build errors detected
by the Maven extension, which can be ignored, but may hinder
Your everyday development activities.
Furthermore, there it may result in many SVN changes, which are
certainly not to be uploaded to the Subversion server.
Therefore, we recommend that You setup a separate Eclipse instance
and a separate developer workspace for the AF3 distillery.
Follow the developer installation as usual.
3. Install Maven Integration for Eclipse¶
- Go to Help -> Install new software
- Enter the following update site: http://download.eclipse.org/releases/kepler.
- Pick m2e - Maven Integration for Eclipse (there might be several, but they should all be equivalent)
- (optional) Enable Debug Output in the Maven section of the Eclipse preferences
- Restart Eclipse (Eclipse should already suggest it)
Ignore errors reported by Eclipse (more precisely by the Maven extension).
Maven does not know about the Tycho build components, but it will when we run the
4. Replace the fortiss-std-env with the distillery-std-env¶
- delete the plugin fortiss-std-env
- Go to File -> Import...
- Choose: Checkout projects from SVN
(warning: so far it looks familiar, but please pay attention to the next step before going further)
- Choose the existing location https://orion.fortiss.org/svn/af3
- Select the project https://orion.fortiss.org/svn/af3/distillery/distillery-std-env and click Next
-> the checkout dialog will propose fortiss-std-env, this is expected; keep it this way
- Click Next again (and not directly Finish as usual)
- Uncheck "Use default workspace location"
- Choose the "plugins" sub-directory of your workspace
- Now hit Finish
This particular procedure is necessary because of a pitfall introduced by buckminster materialization: All the
plugin projects reside in a plugins sub-directory of your workspace location.
Unfortunately, the Maven build is run on the hard disk locations instead of the
Eclipse workspace abstraction.
5. Checkout additional Maven projects¶Apply the same procedure as for distillery-std-env to check out the following projects (yes, they have to be checked out one by one):
(this project replaces af3.rcp.application and is used for custom branding)
(used to build an update site)
(used to build the product from the update site)
(repackaging of a couple of Eclipse features needed to enable the help system in the products)
6. Customize the product to your needs¶
(the reason you are doing this entire procedure)
- Again using the same procedure as before (i.e., ensuring that the location is plugins), check out any additional plugins or branched alternatives you want to
have in the custom project and apply any patches to the plugins already part
of the main product release
- Make sure your plugins contain a pom.xml like all other plugin projects
- Add your plugins to /org.fortiss.af3.phoenix.distillery.p2site.build/pom.xml (use the already
specified plugins as reference template)
- Add your plugins to /org.fortiss.af3.phoenix.distillery.p2site.feature/feature.xml
- Add your plugins to /org.fortiss.af3.phoenix.product.feature/feature.xml
7. Create the product¶
- Right-click /org.fortiss.af3.phoenix.distillery.p2site.build/pom.xml and choose
Run as ... -> Maven Install to build the update site, which is located at
- Right-click /org.fortiss.af3.phoenix.distillery.product.build/pom.xml and choose
Run as ... -> Maven Install to build the product ZIPs, which are located at
You may have to refresh these to projects by hitting F5.
8. Custom Branding¶The distillery branding is located in two of the projects checked out earlier:
- org.fortiss.af3.phoenix.distillery.application contains the splash screen image
and the workbench advisor including the icons registered with it.
You may want to look at the repository revision 13263 of this project to have an
example or use corresponding Eclipse documentation sources.
- org.fortiss.af3.phoenix.distillery.product contains the product file, which is
responsible to configure the native OS launcher application.
You may want to look at the repository revision 13235 of this project to have an
example or use corresponding Eclipse documentation sources.
9. FAQ and Common Problems / Errors¶
MANIFEST.MF vs. pom.xml¶
If your plugin version in META-INF/MANIFEST.MF is "1.0.0.qualifier" then your pom.xml
must contain the version "1.0.0-SNAPSHOT".
Is there a quick way to check if dependencies are all well?¶
Run "Maven Clean" target instead of "Maven Install" on the P2 site build.
Adding a plugin resulted in a dependency error although Eclipse version works perfect?¶
- Check the on-disk location of the missing plugin if it is really next to all others.
- Check if /org.fortiss.af3.phoenix.distillery.p2site.build/pom.xml includes the plugin.
- Check if /org.fortiss.af3.phoenix.distillery.p2site.feature/feature.xml includes the plugin.