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
* The editor type is determined by mapping <code>editorId</code> to an editor
	 * extension registered with the workbench.  An editor id is passed rather than
	 * an editor object to prevent the accidental creation of more than one editor
	 * for the same input. It also guarantees a consistent lifecycle for editors,
	 * regardless of whether they are created by the user or restored from saved 
	 * data.
	 * </p>
	 *
	 * @param input the file to edit
	 * @param editorId the id of the editor extension to use or null
	 * @param activate if <code>true</code> the editor will be activated
	 * @return an open and active editor
	 * @exception PartInitException if the editor could not be initialized
	 */
	public IEditorPart openEditor(IFile input, String editorId, boolean activate)
	throws PartInitException;
	/**
	 * Opens an editor on the given file resource.  
	 * <p>
	 * If this page already has an editor open on the target object that editor is 
	 * activated; otherwise, a new editor is opened. 
	 * <p><p>
	 * The editor type is determined by mapping <code>editorId</code> to an editor
	 * extension registered with the workbench.  An editor id is passed rather than
	 * an editor object to prevent the accidental creation of more than one editor
	 * for the same input. It also guarantees a consistent lifecycle for editors,
	 * regardless of whether they are created by the user or restored from saved 
	 * data.
	 * </p>
	 *