commit | 03b198966216773ce291fa0d7923cc745ddcc38f | [log] [tgz] |
---|---|---|
author | Ralf M Petter <ralf.petter@gmail.com> | Mon Feb 06 17:42:54 2017 +0100 |
committer | Lars Vogel <Lars.Vogel@vogella.com> | Fri Apr 28 12:10:18 2017 -0400 |
tree | e7a420df59b8199a5d0521e232bfd09a4ce806af | |
parent | e492ceb23a6f790d5916f4ae7a972b84582d671e [diff] |
Bug 510830 Many tests in org.eclipse.ui.tests.forms are not executed during Tycho build Changes the names of several JUnit test classes so that the names matche the pattern the surefire plugin of maven uses to finds JUnit tests. Changed the FormImagesTest so that the are no longer influenced by other plugins Change-Id: I3da6e766bf035959e2b94e97e9234fecb2bc0924 Signed-off-by: Ralf M Petter <ralf.petter@gmail.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] 1.
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] 2 page on the team wiki.
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.