| RE: [p2-dev] Strange issues with update site = pulling my hair out |
|
Thanks Pascal. I think that was part of my problem.
Once I set the feature to include the exact version numbers of the plugins then
it seemed to upgrade correctly. The tooling could do a better job making
it obvious you should do this. My (maybe simple) expectation was that
when I clicked Build/Build All, the new update site would include and install
only the latest version of my stuff. I’ll research the uninstall issue more. I’ve
uninstalled and reinstalled so many times now I don’t know whats what
anymore. I’m stuck on 3.5.1 so I can’t really upgrade anytime
soon. Thanks, -Chris From:
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal
Rapicault If the Feature includes the Plugins with a range rather than
strictly including it, then it could explain some of the behavior you are
seeing. Also when you try to uninstall, are you sure that there is
no other plug-in in the system that actually uses 1.0.0.001? In this week I build (toward 3.6 M6) we have released
changes in that space. Maybe you want to give it a try. As for teh 3.5 issue, open a bug with a test case (or
installable snippets of your metadata) and we will start from there. On 2010-03-10, at 10:45 AM, Chris Gross wrote:
I’m
hoping someone here can help me with some really weird behavior I’m
seeing with p2. I’m having multiple problems with what I believe is
a very straight forward scenario. I
have 3 plugins, one feature, and one update site. Installing the
feature/plugins through the update site was easy and successful. My
problems are coming now that I try to release a new version and update those
installations. First
problem: I’ve
got my updated plugins (new code, bug fixes, etc). I incremented the
version number on those plugins (from 1.0.0 -> 1.0.0.001). I updated
the feature version number similarly. Rebuilt the update site.
Redeploy update site. The Eclipse installation notices I have a new
version, downloads the new plugin (or seems to), but then when I use the plugin
– the code seems to be the original code from the 1.0.0 version?!?
And if I look in the Product Details dialog I notice the plugin version is
still 1.0.0..?? Second
problem: In
experimenting to fix this problem, I created a whole new Eclipse installation,
installed the 1.0.0.001 version from the start. Works fine. Now I
tried to uninstall 1.0.0.001 and installed 1.0.0 back in. Now I’m
having a similar problem as above. This time the code still seems to be
at 1.0.0.001 version even though I uninstalled that and installed 1.0.0.
Checking the Product Details dialog shows version 1.0.0 installed. I even
checked the /plugins directory and it shows a 1.0.0 plugin as well. Yet
the actual code that’s getting executed is definitely 1.0.0.001..?! I’ve
tried deleting some of the cache files in the p2 directory. That
didn’t seem to change anything. Please
help. -Chris _______________________________________________ |