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
* <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>
	 * An appropriate editor for the input is determined using a multistep process.
	 * </p>
	 * <ol>
	 *   <li>The workbench editor registry is consulted to determine if an editor 
	 *			extension has been registered for the file type.  If so, an 
	 *			instance of the editor extension is opened on the file.  
	 *			See <code>IEditorRegistry.getDefaultEditor(IFile)</code>.
	 *   <li>Next, the native operating system will be consulted to determine if a native
	 *			editor exists for the file type.  If so, a new process is started
	 *			and the native editor is opened on the file.
	 *   <li>If all else fails the file will be opened in a default text editor.</li>
	 * </ol>
	 * </p>
	 *
	 * @param input the file to edit
	 * @return an open and active editor, or null if a system editor was opened
	 * @exception PartInitException if the editor could not be initialized
	 */
	public IEditorPart openEditor(IFile input) 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 
	 * brought to front; otherwise, a new editor is opened. If 
	 * <code>activate == true</code> the editor will be activated. 
	 * <p><p>