commit | 767fd4d9b74af0e86e02562123ddd667dce3a08e | [log] [tgz] |
---|---|---|
author | Matthias Becker <ma.becker@sap.com> | Tue Jan 16 23:05:10 2018 +0100 |
committer | Lars Vogel <Lars.Vogel@vogella.com> | Mon Jan 22 05:07:57 2018 -0500 |
tree | c2427e69bb981dd38fe6d7934e84e165ad7b041c | |
parent | 940db2eca0d881056077cc3c8d2ba491a5c2dce6 [diff] |
Bug 528831: Use static inner classes where possible - Part 6 If an an inner class, but does not use its embedded reference to the object which created it. This reference makes the instances of the class larger, and may keep the reference to the creator object alive longer than necessary. If possible, the class should be made static. Signed-off-by: Matthias Becker <ma.becker@sap.com> Change-Id: Ic2d02e8a0e6e02d88d0f7a1d2708ae7a83c7ce3c
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.