Bug 26272 Add _$ to list of prefixes for field getter/setter creation [code manipulation]
A common convention is to use _ for instance variables and _$ for static instance variables. Although _ will be stripped by default, it would be useful if _$ was also in the list. Of course, this is settable for individual users (which I've already done) but since it is not an uncommon coding convention (and won't harm anyone in general if present) then I would vote for it to be added to the getter/setter generation prefixes.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
* @see #EDITOR_PROBLEM_INDICATION
	 * @see org.eclipse.jface.resource.StringConverter
	 * @see org.eclipse.jface.preference.PreferenceConverter
	 */
	public final static String EDITOR_PROBLEM_INDICATION_COLOR= "problemIndicationColor"; 
	/**PreferenceConstants.EDITOR_PROBLEM_INDICATION_COLOR;
	 * A named preference that controls whether the editor shows warning indicators in text (squiggly lines). 
	 * <p>
	 * Value is of type <code>Boolean</code>.
	 * </p>
	 */
	public final static String EDITOR_WARNING_INDICATION= "warningIndication"; 
	/**
	 * A named preference that holds the color used to render warning indicators.
	 * <p>
	 * Value is of type <code>String</code>. A RGB color value encoded as a string
	 * using class <code>PreferenceConverter</code>
	 * </p>
	 * 
	 * @see #EDITOR_WARNING_INDICATION
	 * @see org.eclipse.jface.resource.StringConverter
	 * @see org.eclipse.jface.preference.PreferenceConverter
	 */
	public final static String EDITOR_WARNING_INDICATION_COLOR= "warningIndicationColor"; 
	
	/**
	 * A named preference that controls whether the editor shows task indicators in text (squiggly lines). 
	 * <p>
	 * Value is of type <code>Boolean</code>.
	 * </p>