Bug 81140 [nls tooling] Too many false positives when navigating from a key in properties file editor to Java editor
I200412142000 Currently properties key references are determined by a text search. The text search results should be filtered, such that the final results contain only matches from string partitions.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java
}
	}
	
	/**
	 * Searches references to the given key in the given scope.
	 * 
	 * @param scope the scope
	 * @param key the properties key
	 * @return the references or <code>null</code> if the search has been canceled by the user
	 */
	private KeyReference[] search(final IResource scope, final String key) {
		if (key == null)
			return new KeyReference[0];
		final List result= new ArrayList(5);
		try {
			fEditor.getEditorSite().getWorkbenchWindow().getWorkbench().getProgressService().busyCursorWhile(
				new IRunnableWithProgress() {
					public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException {
						ResultCollector collector= new ResultCollector(result, monitor);
						TextSearchEngine engine= new TextSearchEngine();
						engine.search(ResourcesPlugin.getWorkspace(), 
								createScope(scope), false,
								collector, new MatchLocator(key, true, false));
					}
				}
			);
		} catch (InvocationTargetException ex) {
			String message= PropertiesFileEditorMessages.getString("OpenAction.error.messageErrorSearchingKey"); 
			showError(new CoreException(new Status(IStatus.ERROR, JavaUI.ID_PLUGIN, IStatus.OK, message, ex.getTargetException())));
		} catch (InterruptedException ex) {