commit | 61ab7095732880cab41a940445a2c5f1f7527184 | [log] [tgz] |
---|---|---|
author | Andrey Loskutov <loskutov@gmx.de> | Fri Sep 13 05:25:56 2019 -0400 |
committer | Andrey Loskutov <loskutov@gmx.de> | Fri Sep 13 14:27:00 2019 -0400 |
tree | 900e7ac567d6d1dbcc4200b7fd4fd31052987023 | |
parent | ae4dd6aea39dc6a4b2ef24c4939fb8151b3e947c [diff] |
Revert "Revert "Bug 550828 - Activate heap monitor by default"" This reverts commit 5fd38435f5ba216eeb3a2ffe4b53e310ccbac46d. We assume the bug 551029 can be fixed in jdt debug test framework, see http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=cf00ba80bc80a6eacde52b2090e55687e6f2f540. Change-Id: I9c5540d927362d4bc19764621e2ea09b4931f631
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.