| Can the platform manage multiple versions of a plugin at once? [message #290463] |
Thu, 25 August 2005 12:13  |
Eclipse User |
|
|
|
Originally posted by: csetera.spss.com
Let's say that I have a situation where I have two features A and B that
depend on plugins in feature C. Now, let's say that feature A is
updated and needs a newer version of plugins in feature C, while feature
B still needs the previous versions. If feature A and C are updated,
can feature B continue to use the older version of feature C and its
plugins? It seems that this should be somewhat possible given the
classloader implementation in the platform, but I'm not sure if it would
work. If it does work, how far does it go? For instance, is it
possible for the platform to manage multiple versions of SWT given that
it also has native code?
Thanks,
Craig
|
|
|
|
| Re: Can the platform manage multiple versions of a plugin at once? [message #290483 is a reply to message #290463] |
Thu, 25 August 2005 13:11  |
| Eclipse User |
|
|
|
Craig Setera wrote:
> Let's say that I have a situation where I have two features A and B that
> depend on plugins in feature C. Now, let's say that feature A is
> updated and needs a newer version of plugins in feature C, while feature
> B still needs the previous versions. If feature A and C are updated,
> can feature B continue to use the older version of feature C and its
> plugins? It seems that this should be somewhat possible given the
> classloader implementation in the platform, but I'm not sure if it would
> work. If it does work, how far does it go? For instance, is it
> possible for the platform to manage multiple versions of SWT given that
> it also has native code?
I think there was a thread on this about 1-2 months ago ... the OSGi
runtime can run multiple Bundles, but eclipse can't.
Check out the MANIFEST.MF file, the eclipse plugins are defined like:
Bundle-SymbolicName: org.eclipse.ui.tests; singleton:=true
and singleton:=true means only one instance of the plugin can be active
(I think, although I have no proof).
Later,
PW
|
|
|
| Re: Can the platform manage multiple versions of a plugin at once? [message #290503 is a reply to message #290463] |
Thu, 25 August 2005 15:05 |
| Eclipse User |
|
|
|
Originally posted by: john.eclipsefaq.org
Multiple versions of the same plugin can be active at once, but only if
they do not define extensions or extension points. From the runtime's
point of view, there could be two versions of SWT active at once. In
practice this isn't likely to suceed because each will create its own
display, etc. In the case of SWT, it is fully backwards compatible so
plugins based on an older version should still work with a newer release.
--
Craig Setera wrote:
> Let's say that I have a situation where I have two features A and B that
> depend on plugins in feature C. Now, let's say that feature A is
> updated and needs a newer version of plugins in feature C, while feature
> B still needs the previous versions. If feature A and C are updated,
> can feature B continue to use the older version of feature C and its
> plugins? It seems that this should be somewhat possible given the
> classloader implementation in the platform, but I'm not sure if it would
> work. If it does work, how far does it go? For instance, is it
> possible for the platform to manage multiple versions of SWT given that
> it also has native code?
>
> Thanks,
> Craig
|
|
|
Powered by
FUDForum. Page generated in 0.02997 seconds
Home