|Re: Why can't I pull in org.eclipse.ui.workbench to my MANIFEST file? [message #634236 is a reply to message #634183]
||Wed, 20 October 2010 21:30
| Alex Le
Registered: July 2009
On 10/20/10 10:14 AM, AL wrote:|
> On 10/19/10 10:40 PM, Prakash G.R. wrote:
>> On 20/10/10 7:11 AM, AL wrote:
>>> Upgraded to Eclipse 3.5.2, my plug-ins fail to compile because the
>>> Activator.java class extends the org.eclipse.ui.plugin.AbstractUIPlugin
>>> class, which is in the org.eclipse.ui.workbench plug-in. My own plug-in
>>> never needed to pull in the org.eclipse.ui.workbench plug-in, which is
>>> shown in the "Plug-ins" view of the PDE perspective. My Activator.java
>>> class only imports org.eclipse.ui.plugin.AbstractUIPlugin class.
>>> 1. Is this a big change in Eclipse 3.5.2? I have to pull in the
>>> org.eclipse.ui.workbench plug-in, as a dependency, into my own plug-in's
>>> MANIFEST now?
>> You should be adding org.eclipse.ui plugin as your dependency - not the
>> workbench one.
> That's currently what I have, and my plug-in fails to compile due to
> unresolved org.eclipse.ui.plugin.AbstractUIPlugin class.
eclipse -clean or "F5" on the workspace helps! :-)
Powered by FUDForum
. Page generated in 0.03050 seconds