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
try {
			fStorage= storageEditorInput.getStorage();
		} catch (CoreException e) {
			fStorage= null;
		}
	}
	/*
	 * @see org.eclipse.jdt.internal.ui.javaeditor.IHyperlink#getHyperlinkRegion()
	 */
	public IRegion getHyperlinkRegion() {
		return fRegion;
	}
	/*
	 * @see org.eclipse.jdt.internal.ui.javaeditor.IHyperlink#open()
	 */
	public void open() {
		if (!checkEnabled())
			return;
	
		
		IResource resource= (IResource)fStorage;
		KeyReference[] references= null;
		if (resource != null)
			references= search(resource.getProject(), fPropertiesKey);
		
		if (references == null)
			return; 
		
		if (references.length == 0) {
			String message= PropertiesFileEditorMessages.getString("OpenAction.error.messageNoResult");