Bug 176986 [Markers] Move tasks into the problems view
We should consider moving the tasks into the problem view as currently no one is using them in the tasks view. The main issue this could create is performance - problems change rapidly but tasks are generally pretty static and it may be a fair amount of extra time spent sorting them.
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerSupportRegistry.java
import org.eclipse.core.runtime.dynamichelpers.ExtensionTracker;
import org.eclipse.core.runtime.dynamichelpers.IExtensionChangeHandler;
import org.eclipse.core.runtime.dynamichelpers.IExtensionTracker;
import org.eclipse.osgi.util.NLS;
import org.eclipse.ui.PlatformUI;
import org.eclipse.ui.internal.ide.IDEWorkbenchPlugin;
import org.eclipse.ui.internal.views.markers.MarkerContentGenerator;
import org.eclipse.ui.internal.views.markers.MarkerSupportInternalUtilities;
import org.eclipse.ui.views.markers.MarkerField;
import org.eclipse.ui.views.markers.MarkerSupportConstants;
/**
 * The ProblemFilterRegistryReader is the registry reader for declarative
 * problem filters. See the org.eclipse.ui.markerSupport extension point.
 * 
 * @since 3.2
 * 
 */
public class MarkerSupportRegistry implements IExtensionChangeHandler {
	private static final String DESCRIPTION = "onDescription"; 
	/**
	 * The enabled attribute.
	 */
	public static final String ENABLED = "enabled"; 
	private static final Object ERROR = "ERROR";
	private static final Object INFO = "INFO";
	private static final Object WARNING = "WARNING";
	private static final String MARKER_ID = "markerId"; 
	/**
	 * The tag for the marker support extension
	 */