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
new String[] { wbAdapter.getLabel(keyReference), x.getLocalizedMessage() } );
			if (message == null)
				message= PropertiesFileEditorMessages.getFormattedString("OpenAction.error.message", x.getLocalizedMessage()); 
			
			MessageDialog.openError(fShell,
				PropertiesFileEditorMessages.getString("OpenAction.error.messageProblems"), 
				message);			
		}		
	}
	
	private String getErrorDialogTitle() {
		return PropertiesFileEditorMessages.getString("OpenAction.error.title"); 
	}
	
	private void showError(CoreException e) {
		ExceptionHandler.handle(e, fShell, getErrorDialogTitle(), PropertiesFileEditorMessages.getString("OpenAction.error.message")); 
	}
	
	private void showErrorInStatusLine(final String message) {
		fShell.getDisplay().beep();
		final IEditorStatusLine statusLine= (IEditorStatusLine)fEditor.getAdapter(IEditorStatusLine.class);
		if (statusLine != null) {
			fShell.getDisplay().asyncExec(new Runnable() {
				/*
				 * @see java.lang.Runnable#run()
				 */
				public void run() {
					statusLine.setMessage(true, message, null);
				}
			});