commit | 180453677480695b60afd1ee8bf2a8badad8693b | [log] [tgz] |
---|---|---|
author | Matthias Becker <ma.becker@sap.com> | Fri Dec 08 13:14:42 2017 +0100 |
committer | Lars Vogel <Lars.Vogel@vogella.com> | Mon Dec 11 07:53:33 2017 -0500 |
tree | 53e98c921dd193c7776a82434201eae2c0016d39 | |
parent | 84b4e32ecec1772a97e8adabaa257b86c46b2eb3 [diff] |
Bug 528318: Use Array List Instead Of Vector Early classes of the Java API, such as Vector were synchronized to make them thread-safe. Unfortunately, synchronization has a big negative impact on performance, even when using these collections from a single thread. It is better to use their new unsynchronized replacements like ArrayList or LinkedList instead of Vector Change-Id: I61d418e4e87f17c96d837573b62d672de95eae9f Signed-off-by: Matthias Becker <ma.becker@sap.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.
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.