tag | 4350dca28d80681a6cdf9051a67c1b56992bc875 | |
---|---|---|
tagger | Eclipse Platform RelEng Bot <releng-inbox@eclipse.org> | Fri Aug 24 02:59:18 2018 -0400 |
object | 3791d9848f016052fd9236c8baee7f8254e3e2a1 |
4.9M3
commit | 3791d9848f016052fd9236c8baee7f8254e3e2a1 | [log] [tgz] |
---|---|---|
author | Eclipse Platform RelEng Bot <releng-inbox@eclipse.org> | Thu Aug 23 04:39:04 2018 -0400 |
committer | Eclipse Platform RelEng Bot <releng-inbox@eclipse.org> | Thu Aug 23 04:39:04 2018 -0400 |
tree | 18b241508f616f305b30b57053d1f3c622693f77 | |
parent | 2c289fa0e91570b38a2e76bfd830b0cec6912be8 [diff] |
Build input for build I20180823-0430
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.