Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 241037

Summary: caching problem w/ Eclipse 3.4's p2 install manager
Product: [Eclipse Project] Equinox Reporter: David Muir <david>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: david
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Muir CLA 2008-07-15 23:04:42 EDT 
I've been using the PDT 2.0 nightlies for a while now, but whenever I try to update to a newer version. It complains and says that the new version is already installed. Or it tries to install an older version which isn't even in the local "update site". I've tried removing the update site, re-adding it. Refreshing. Uninstalling PDT, then reinstalling with a fresh update site, but it still finds the old version and installs it instead. Is there a way to force-clear the cache?
Comment 1 David Muir CLA 2008-07-16 00:53:03 EDT 
Should also add, that I've tried running `eclipse -clean` as well.
When I go to software updates, and refresh the local site, it shows the version already installed instead of the one that was just unzipped there (refreshing doesn't help).
Comment 2 John Arthorne CLA 2008-07-16 14:05:58 EDT 
From looking at the PDT nightly builds, I can see they use a version number of "2.0.0.HEAD". This also means that every build has the same version number, so p2 can't make any sense of it. They need to have unique version numbers per build for install/update technology to work properly.