Bug 136337 [IDE] Allow a user to force the removal of all problem markers
We've ran into situations when we see stray problem markers in the problems view. These markers cannot be deleted anymore because the code (builder)supposed to take care of them either is not around anymore or simply cannot identify them by type or by some other attribute. Currently, the only way to get rid of these markers is by deleting the metadata. The platform could provide an action which a user could use to remove all problem markers from the problems view. To keep the workspace in a consistent state, it may be that after deleting the markers, the action will have to trigger a full build.
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerMessages.java
public static String MarkerResolutionDialog_Title;
	public static String MarkerResolutionDialog_CalculatingTask;
	public static String MarkerResolutionDialog_WorkingSubTask;
	public static String MarkerResolutionDialog_AddOthers;
	public static String ProblemView_GroupByMenu;
	public static String ProblemView_Type;
	public static String ProblemView_None;
	public static String ProblemView_UpdateCategoryJob;
	public static String Util_ProjectRoot;
	public static String Util_WorkspaceRoot;
	public static String DialogMarkerProperties_CreateMarker;
	public static String DialogMarkerProperties_ModifyMarker;
	public static String DialogMarkerProperties_Create;
	public static String DialogMarkerProperties_Modify;
	public static String DialogTaskProperties_CreateTask;
	public static String modifyBookmark_title;
	public static String modifyTask_title;
	public static String qualifiedMarkerCommand_title;
	public static String task_title;
	public static String problem_title;
	public static String bookmark_title;
	public static String PasteHandler_title;
	public static String AND_Title;
	public static String OR_Title;
	public static String ContentGenerator_NoGrouping;
	public static String newViewTitle;
	public static String NewViewHandler_dialogTitle;
	public static String NewViewHandler_dialogMessage;
}