| commit | c0fdc8d74c6e609586eebf0558c805e058a308e7 | [log] [tgz] |
|---|---|---|
| author | Rolf Theunissen <rolf.theunissen@gmail.com> | Sun Dec 27 15:27:29 2020 +0100 |
| committer | Alexander Kurtakov <akurtako@redhat.com> | Wed Apr 21 03:29:20 2021 -0400 |
| tree | 645514f44e3d3b957c476e65e3faa8f4200a4ffd | |
| parent | e39a1c096178d94c522244eaf4f47a17ee1df0c8 [diff] |
Bug 366633 - [Tests] ResourceMappingMarkersTest fails Use reflective method call to get the Tree widget, instead of the (failing) cast on the first child widget. Ensure that TestProject is cleaned up in other test cases. Change-Id: I4302c4708b5e0acb00aa7ad0b4edf9772d939842 Signed-off-by: Rolf Theunissen <rolf.theunissen@gmail.com> Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.ui/+/174120 Tested-by: Platform Bot <platform-bot@eclipse.org> Reviewed-by: Alexander Kurtakov <akurtako@redhat.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 libraries. Please install them from the Orbit Download page]3:
Currently the following plug-ins 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.