|Re: P2 tries to update to an older version => FAILS [message #826384 is a reply to message #824545]
||Wed, 21 March 2012 21:56
| Matthieu Rethers
Registered: March 2012
Thanks for the article. I understand there is a conflict but what I don't understand is why this is happening.|
- why would p2 want to "downgrade" to an earlier version of the product?
- why won't p2 detect that I already have the latest version?
- why does it work just fine if I remove 2.0.2 from the update site?
I should have mentionned that this is an automatic update check on startup based on the example in the RCP wiki. In this case, I would expect p2 to just tell me that there is nothing to update.
This product is based on feature and I changed the version number of my product plugin and feature to 2.0.3 before rebuilding. Checked export metadata when building. Updated the repo with the files. This is as straight forward as it gets but I'm probably missing something here. So frustrating, I chose eclipse especially for P2 but now it's dragging my project down.
Powered by FUDForum
. Page generated in 0.04383 seconds