| OSGI BundleActivator cannot be resolved [message #128946] |
Sat, 20 December 2003 20:07  |
Eclipse User |
|
|
|
Originally posted by: schmerl+gef.cs.cmu.edu
Hi,
Moving to M6, my plugin no longer compiles. The plugin.java file is flagged
with the following error:
The type org.osgi.framework.BundleActivator cannot be resolved. it is
indirectly referenced from required .class file.
I have the OSGI jars selected in my target plaform. What more do I need to
do?
Any help would be greatly appreciated.
Thanks,
Bradley.
|
|
|
|
| Re: OSGI BundleActivator cannot be resolved [message #130107 is a reply to message #129011] |
Sun, 28 December 2003 02:18  |
| Eclipse User |
|
|
|
Originally posted by: ed.burnette.REMOVE.THIS.sas.com
Or instead of org.eclipse.osgi, add org.eclipse.core.runtime.compatibility
to plugin.xml. Editing .classpath shouldn't be necessary (wasn't for me, at
least).
I could be wrong but I believe this is only a problem for those of us
following along with the 3.0M* versions - somebody converting directly from
2.1.x shouldn't have to do that manually.
--
Ed Burnette, co-author, Eclipse in Action
www.eclipsepowered.org
"Eric Clayberg" <clayberg@instantiations.com> wrote in message
news:bs2tpd$8h2$1@eclipse.org...
> Add the following JARs to your .classpath file...
>
> ECLIPSE_HOME/plugins/org.eclipse.osgi_3.0.0/osgi.jar
> ECLIPSE_HOME/plugins/org.eclipse.osgi_3.0.0/eclipseAdaptor.j ar
>
> You will also need to add the following import to your plugin.xml...
>
> <import plugin="org.eclipse.osgi" optional="true"/>
>
|
|
|
|
| Re: OSGI BundleActivator cannot be resolved [message #130297 is a reply to message #130216] |
Mon, 29 December 2003 06:11 |
| Eclipse User |
|
|
|
Originally posted by: ed.burnette.REMOVE.THIS.sas.com
"Eric Clayberg" <clayberg@instantiations.com> wrote in message
news:bsmpuh$ne4$1@eclipse.org...
> "Ed Burnette" <ed.burnette@REMOVE.THIS.sas.com> wrote in message
> news:bslega$nkj$1@eclipse.org...
> > I could be wrong but I believe this is only a problem for those of us
> > following along with the 3.0M* versions - somebody converting directly
> from
> > 2.1.x shouldn't have to do that manually.
>
> I'm not sure what you mean here. On our end, we are keeping our plugins
> compatoble with Eclipse 2.0, 2.1 and 3.0 simultaneously.
That's a nice trick; I remember a posting you made about that a while back.
I see that you're going to be presenting something on this at EclipseCon
(www.eclipsecon.org) and I'm looking forward to it.
However, I expect most plug-in developers (esp. non-commercial ones) will
still target only one major version of Eclipse. When you bring a 2.1 plug-in
into 3.0 there's a wizard to convert it, making it incompatible with 2.1.
One of the things this wizard should do is insert any new necessary
dependencies. Since I converted my plug-ins early in the 3.0M* cycle, I
didn't get the benefit of that (even M6 doesn't completely do it). But
somebody converting directly from 2.1.x production to the production 3.0
hopefully won't have the problems.
--
Ed
|
|
|
Powered by
FUDForum. Page generated in 0.03410 seconds
] 
Search
Help
Register
Login
Home
