|p2 repository produces outdated jar/plugin [message #1060151]
||Thu, 23 May 2013 10:44
| Erik Vande Velde
Registered: September 2012
Our project consists of a common, server and client module.|
Common contains classes that are shared between the server and client.
The client module (RCP4) should always use the most recent version of common.
Therefore we build a common-1.0.0-SNAPSHOT jar, and put it in nexus.
We also have a p2repository module that creates a p2 update site containing the latest common code, let's call it p2repository.zip.
THE PROBLEM: when we use p2repository.zip as 'software site' in the target platform of our client module it somehow downloads the common-1.0.0-SNAPSHOT.jar of one day ago, and the code doesn't compile. Still that same zip contains the correct version of common-1.0.0-SNAPSHOT.jar in its plugin sub-directory, so I wonder where eclipse finds the outdated jar.
THE QUESTION: why doesn't eclipse use the jars in the p2 repository zip, and where does it find the outdated jars it does use?
Sadly I cannot attach the p2repository.zip here, as it's 4 MB in size ...
Powered by FUDForum
. Page generated in 0.01598 seconds