commit | 91f7343a6ef89e6a5077cb9c1fd71855a2cc62cb | [log] [tgz] |
---|---|---|
author | Alexander Kurtakov <akurtako@redhat.com> | Fri Jul 21 14:18:07 2017 +0300 |
committer | Alexander Kurtakov <akurtako@redhat.com> | Fri Jul 21 07:21:44 2017 -0400 |
tree | 7dfac13f9eb81ab678e3e6a43bd1c80e0efe9b7c | |
parent | 0ecd8e83cbc7cc492aaf4a45a824921d04952ece [diff] |
Bug 520005 - Enforce maven-clean-plugin 3.0.0 via pluginManagement SWT uses maven-clean-plugin to ensure proper builds and has set version to 3.0.0 in the pom. eclipse-parent pom doesn't specify anything and this results in 2.5 na 3.0 versions of the plugin used in different places. Let's specify the newer version and have everything use it. Change-Id: Ida3a87fe447a8c9565cacf0f5ca92e0bf3662a6a Signed-off-by: Alexander Kurtakov <akurtako@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.