commit | 66e661501140b5bd9486be1906f55ac4ed8742b5 | [log] [tgz] |
---|---|---|
author | jay <jarthana@in.ibm.com> | Wed Oct 03 14:16:00 2018 +0530 |
committer | jay <jarthana@in.ibm.com> | Wed Oct 03 14:18:30 2018 +0530 |
tree | c594d32d62312d6deb90a2e98e2d2e8a5fc7d57a | |
parent | dbe8c19fe82cd3d5d789103ae1d58b57545194c7 [diff] |
Bug 538956: [JUnit 5] Incorrect JUnit 5 test results without JUnit 4 on the classpath Including the junit.runtime bundle to the patch build Change-Id: Ic0bc75576295e15e374c53475891299726565814 Signed-off-by: jay <jarthana@in.ibm.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.