| commit | 8c7a5fc64e7e39119999bc76f8391054260f3f31 | [log] [tgz] |
|---|---|---|
| author | Mickael Istria <mistria@redhat.com> | Mon Jan 22 15:40:11 2018 +0100 |
| committer | Mickael Istria <mistria@redhat.com> | Mon Jan 22 16:44:09 2018 +0100 |
| tree | 05ea455bc8ae90a5f9c4d1c4175e6166de114883 | |
| parent | f9aa08342ebb15ff096cbf663fbede6d34de39a5 [diff] |
Bug 530093 - Product to include more recent JRE installable unit a.jre.javase 1.6.0 was used as default. Since p2 now understands BREE and osgi.ee requirements, it has highlighted that this version of the JRE iu isn't sufficient to resolve more recent bundles. Moved to the maximum known compatible version: JavaSE-9. Change-Id: I925b3b69163029c5e4534e1ed4290b8450f3af49 Signed-off-by: Mickael Istria <mistria@redhat.com>
Aggregator repo for Eclipse SDK builds.
To run a complete build, on your local machine, run the commands from ./scripts/build.sh in this folder.
These commands requires the installation and setup of Java 1.8 or higher and Maven version 3.3.3 or higher Plus, other settings, alternatives, and other recommendations are made in the complete instructions on the Platform Build wiki. Note, it is highly recommended to use toolchains.xml and -Pbree-libs as decribed in Using BREE Libs. If you do use BREE Libs (with proper toolchains.xml file) you can use Java 1.7 to “run the build”.
Eclipse Platform Project committers should also read Automated Platform Builds.
Release Engineers should also be familiar with other documents on the Releng Wiki.