Bug 563485 - Refactor StringMatcher into TextMatcher

Re-implement the matcher using org.eclipse.core.text.StringMatcher
and rename it to TextMatcher to avoid confusions. Fix the prefix
matching on individual words if wildcards are to be taken literally.

Add tests for the new TextMatcher.

The old StringMatcher is kept because it is used (despite being
internal!) in org.eclipse.equinox.p2.ui.discovery. Once it'll have
been replaced there by TextMatcher, StringMatcher can be removed.

Change-Id: Ib5bcb0617a6c894d0b0b2bff25d1d4ab279210a7
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>
9 files changed
tree: 75b879344b2868d091e441322ff8e98cdde95694
  1. .gitignore
  2. .mvn/
  7. README.md
  8. bundles/
  9. examples/
  10. features/
  11. pom.xml
  12. releng/
  13. tests/

Contributing to Eclipse Platform UI project

Thanks for your interest in this project.

Project description:

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.

How to contribute:

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.

Test dependencies

Several test plug-ins have a dependency to the Mockito and Hamcrest libraries. Please install them from the Orbit Download page]3:

Currently the following plug-ins are required:

  • net.bytebuddy.byte-buddy
  • net.bytebuddy.byte-buddy-agent
  • org.hamcrest.core
  • org.mockito
  • org.objenesis

How to build on the command line

You need Maven 3.3.1 installed. After this you can run the build via the following command:

mvn clean verify -Pbuild-individual-bundles

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

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) 2.0