commit | fa379a23dc31de685ad2059a50077da5a0a38be9 | [log] [tgz] |
---|---|---|
author | Rolf Theunissen <rolf.theunissen@altran.com> | Wed Nov 21 07:59:22 2018 +0100 |
committer | Andrey Loskutov <loskutov@gmx.de> | Sun Jan 06 01:54:05 2019 -0500 |
tree | 0d6d13cf5acdb5f6628497334087c738752c64ca | |
parent | 2b76f58e4d9cdb165b6116e4c166e1741a9ee85c [diff] |
Bug 530131 - selection not updated in properties view when the properties and the outline views are stacked Regression from bug 485154: If the properties view is hidden do not react on activation of parts in the same stack. Fix: If the Properties view is hidden do not react on activation of a part if the contributing part is in the same stack as the Properties view. Change-Id: I0ff0e6b51d5bf26c2d6a90738d3173332df713c1 Signed-off-by: Rolf Theunissen <rolf.theunissen@altran.com> Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
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]