commit | 9dfea3caf352dce4930f45b5d691f1c5e77dfa39 | [log] [tgz] |
---|---|---|
author | Lars Vogel <Lars.Vogel@vogella.com> | Thu May 17 12:16:11 2018 +0200 |
committer | Karsten Thoms <karsten.thoms@itemis.de> | Wed Nov 07 13:34:29 2018 +0100 |
tree | 88f432e279eb516a610175c272dfdccdfa8f27ef | |
parent | 780b4ca88b513125bca2582f545dfe6970ecc495 [diff] |
Bug 534803 - Migration org.eclipse.e4.ui.tests.css.core to JUnit5 Version bump for 4.10 Added dependencies on JUnit 5 libraries on compile-time dependencies only. Runtime dependency on jupiter engine is added by JUnit 5 classpath container. A compile time dependency can lead to problems with tycho-surefire plugin (see bug#534587). Refactored test classes to use JUnit 5 API. StyledRuleTest: assertEquals for floats with delta of 0f is not valid in JUnit5 Assertions. When a delta is specified, it must be a positive value. Change-Id: Ia6c6db1ac2f84cd80c0ba16402071f25f68954b6 Also-by: Karsten Thoms <karsten.thoms@itemis.de> Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com>
Thanks for your interest in this project.
Platform UI provides the basic building blocks for user interfaces built with Eclipse.
Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.
Website: http://www.eclipse.org/platform/ui/
For more information, refer to the Platform UI wiki page.
Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the Platform UI - How to contribute wiki page page on the team wiki.
Several test plug-ins have a dependency to the Mockito and Hamcrest library. Please install them from the Orbit Download page
Currently the following versions are required:
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.
[Eclipse Public License (EPL) v1.0][4]