Multiple versions of library wrapper plugins [message #586455] |
Thu, 04 December 2008 18:04 |
Eric Rizzo Messages: 3070 Registered: July 2009 |
Senior Member |
|
|
In our RCP application we have a number of "JAR wrapper" bundles
(created with the "Plug-in from existing JAR" project wizard).
Unfortunately, they were originally created and distributed with
qualifiers in their versions, so the versions look like
3.2.0.200809231150. When we do new builds, those plugins get built, too,
using new version numbers like 3.2.0.200812040800 and included in our
update site.
When I do an update from the previous version of our app to a new one
using a just-built update site, it correctly updates everything and
restarts. Upon restart, all of our "real" plugins load the latest
version only (according to Help > About > Plug-in Details) as expected,
but all of those JAR wrapper plugins end up showing up twice, both the
old versions and the new ones.
Can anyone explain why both versions get loaded at runtime? I've checked
and when we express dependency on them we specify the version without
the qualifier (as in 3.2.0), so I don't know what could be triggering
the load of the old versions.
Any ideas? Help debugging?
Thanks in advance,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.02496 seconds