Bug 300032 [Markers] NPE in MarkerFieldFilterGroup.selectByScope
I20100115-1100 I had a Java editor open and dirty. The Problems view was NOT visible (topmost in that view stack was Progress). I pressed 'Alt+Shift+W, P, Return' to reveal the file in the Package Explorer. The stored file had no compile problems, but the the working copy in the editor had a problem which I fixed shortly before I started the Show In action. java.lang.NullPointerException at org.eclipse.ui.internal.views.markers.MarkerFieldFilterGroup.selectByScope(MarkerFieldFilterGroup.java:693) at org.eclipse.ui.internal.views.markers.MarkerContentGenerator.select(MarkerContentGenerator.java:781) at org.eclipse.ui.internal.views.markers.MarkerContentGenerator.internalGatherMarkers(MarkerContentGenerator.java:1073) at org.eclipse.ui.internal.views.markers.MarkerContentGenerator.gatherMarkers(MarkerContentGenerator.java:1013) at org.eclipse.ui.internal.views.markers.MarkerContentGenerator.generateMarkerEntries(MarkerContentGenerator.java:991) at org.eclipse.ui.internal.views.markers.MarkerUpdateJob.clean(MarkerUpdateJob.java:117) at org.eclipse.ui.internal.views.markers.MarkerUpdateJob.buildMarkers(MarkerUpdateJob.java:77) at org.eclipse.ui.internal.views.markers.MarkerUpdateJob.run(MarkerUpdateJob.java:57) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerContentGenerator.java
* 
	 * @return list of resource we want to collect markers for taking various
	 *         enabled filters into account.
	 * 
	 */
	Collection getResourcesForBuild() {
		currentResources = MarkerResourceUtil.computeResources(
				getSelectedResources(), getEnabledFilters(), andFilters());
		return currentResources;
	}
	
	/*
	 * See Bug 296695: This method is trickier than it may seem/appears to be.If
	 * it is ever desired to use this, it would need to be *RE-IMPLEMENTED* and
	 * would need a good amount of testing with various combination of filters
	 * and scopes. The key here is to understand and getting it right how filter
	 * scope and our trimmed, optimized resources and selected resource elements
	 * interact. 
	 * Another possible way to check if content has changed is by
	 * comparing the markers gathered freshly with the previously gathered
	 * markers(cache them when an update is not canceled), whether this up to a
	 * visible limit, or completely, or selected filters we have to see. I am
	 * assuming that this takes little time to do. If this is done prior to
	 * sorting a good amount of time can be saved; we still save the UI time if
	 * checked after sorting. In the sorted case we can use a Binary search as
	 * well.Anyhow if this does take up time, we should skip this method.
	 */
 
 
/