| commit | ddf4388d78d8d02b7ced0c43a7d6a4fc706851af | [log] [tgz] |
|---|---|---|
| author | Ralf M Petter <ralf.petter@gmail.com> | Wed Jan 11 10:05:25 2017 +0100 |
| committer | Ralf Petter <ralf.petter@gmail.com> | Thu Jan 12 10:50:53 2017 -0400 |
| tree | 29d28afc3392d234442f4b5a50cd5165bef5fc3d | |
| parent | 34c5272f4294edaa260195f6c06bc2b86633f78d [diff] |
Bug 259846 - Text is trimed even when setWhitespaceNormalized is set to false for FormText Changes the algorithm in FormTextModel so that the normalization of whitespace works as described in the javadoc of method setWhitespaceNormalized() in FormText. Added unit tests to prove that the new algorithm works as designed. Change-Id: Ie0444e512c8c19d00bddd4a5b239a027eba72a40 Signed-off-by: Ralf M Petter <ralf.petter@gmail.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] 1.
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] 2 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.