Bug 89013 Changes to ResultCollector --> API
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/ResultCollector.java
case CompletionProposal.ANNOTATION_ATTRIBUTE_REF:
				return proposal.getRelevance() * multiplier  + 4;
			case CompletionProposal.POTENTIAL_METHOD_DECLARATION:
				return proposal.getRelevance() * multiplier  + 4 ;
			case CompletionProposal.FIELD_REF:
				return proposal.getRelevance() * multiplier  + 5;
			case CompletionProposal.LOCAL_VARIABLE_REF:
			case CompletionProposal.VARIABLE_DECLARATION:
				return proposal.getRelevance() * multiplier  + 6;
			default:
				return proposal.getRelevance() * multiplier;
		}
	}
	
	/**
	 * Creates a new java completion proposal from a core proposal. This may
	 * involve computing the display label and setting up some context.
	 * <p>
	 * This method is called for every proposal that will be displayed to the
	 * user, which may be hundreds. Implementations should therefore defer as
	 * much work as possible: Labels should be computed lazily to leverage
	 * virtual table usage, and any information only needed when
	 * <em>applying</em> a proposal should not be computed yet.
	 * </p>
	 * <p>
	 * Implementations may return <code>null</code> if a proposal should not
	 * be included in the list presented to the user.
	 * </p>
	 * <p>
	 * Subclasses may extend or replace this method.