| Can't get rid of old bundle version [message #126317] |
Mon, 23 February 2009 20:54 |
 Mirko Raner
Messages: 125
Registered: July 2009
Location: New York City, NY |
Senior Member |
|
|
Hi,
I've been having intermittent troubles with bundle updating ever since
moving to 3.4. I've somewhat gotten used to tinkering with the
platform.xml or the org.eclipse.equinox.simpleconfigurator/bundles.info
file when just visiting an update site didn't do the trick, but this time
I have a problem that I can't figure out. I upgraded a feature from
version 1.0.0.x to 1.0.0.y using the standard update site mechanism In the
"About Eclipse SDK" dialog, the feature appears with the updated build
number, but based on the available functionality, I can tell that the code
being executed is still the code from the previous version. However,
looking at the JAR file in the plugins folder, I noticed that the JAR file
did indeed get replaced by the newer one (the JAR file itself doesn't
carry a full version number with a build number, but I checked the JAR
contents). The old JAR is nowhere to be found, but still Eclipse uses the
old code, even after restarting with -clean. I wiped out the conspicuous
org.eclipse.equinox.p2.metadata.repository/cache folder, but still Eclipse
is picking up the old JAR from somewhere.
Has anyone come across an issue like that and knows how to expunge the old
JAR file from Eclipse's memory? Due to the large number of custom plug-ins
that I use I don't want to start a new Eclipse installation...
Any pointers and suggestions are sincerely appreciated!
Thanks,
Mirko
|
|
|
Powered by
FUDForum. Page generated in 0.03437 seconds
] 
Search
Help
Register
Login
Home
