Bug 67950 [RCP] [doc] ui.workbench.compatibility methods should have deprecation warnings
Build 3.0 RC3 The old IWorkbenchPage methods declared in o.e.ui.workbench.compatibility.ICompatibleWorkbenchPage should have deprecation warnings in case someone imports the plug-in fragment into the workspace and arranges to compile code against it.
bundles/org.eclipse.ui.workbench.compatibility/src/org/eclipse/ui/internal/ICompatibleWorkbenchPage.java
* <code>activate == true</code> the editor will be activated.  The cursor and 
	 * selection state of the editor are then updated from information recorded in 
	 * the marker.
	 * <p><p>
	 * If the marker contains an <code>EDITOR_ID_ATTR</code> attribute 
	 * the attribute value will be used to determine the editor type to be opened. 
	 * If not, the registered editor for the marker resource will be used. 
	 * </p>
	 *
	 * @param marker the marker to open
	 * @param activate if <code>true</code> the editor will be activated
	 * @return an open editor, or null if a system editor was opened
	 * @exception PartInitException if the editor could not be initialized
	 * @see IEditorPart#gotoMarker
	 */
	public IEditorPart openEditor(IMarker marker, boolean activate) 
	throws PartInitException;
	
	/**
	 * Opens an operating system editor on a given file. Once open, the
	 * workbench has no knowledge of the editor or the state of the file
	 * being edited.  Users are expected to perform a "Local Refresh" from
	 * the workbench user interface.
	 *
	 * @param input the file to edit
	 * @exception PartInitException if the editor could not be opened.
	 */
	public void openSystemEditor(IFile input) throws PartInitException;
}