|Multiple versions of library wrapper plugins [message #35885]
||Thu, 04 December 2008 18:04
Originally posted by: eclipse-news.rizzoweb.com|
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
18.104.22.168809231150. When we do new builds, those plugins get built, too,
using new version numbers like 22.214.171.124812040800 and included in our
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,
Powered by FUDForum
. Page generated in 0.03253 seconds