P2 and link files error [message #113242] |
Thu, 03 July 2008 17:12 |
Eclipse User |
|
|
|
Originally posted by: fireresq.embarqmail.com
Think this is the correct group for this. If not please let me know where to ask this question.
1) Install a clean eclipse 340 classic
2) Install simple feature com.foo in ...
/opt/mystuff_a/eclipse
features/
com.foo.feature_v1.2.3.a
plugins/
com.foo_v1.2.3.a
3) create a link file that points to the installed code
/opt/eclipse-340-classic/dropins
com.foo.a.link :: path=/opt/mystuff_a
4) start eclipse and mystuff is working as expected.
look at the software updates and addons page and that plugin is loaded and present with version 1.2.3.a
5) stop eclipse
6) install a new version of com.foo on disk
/opt/mystuff_b/eclipse
features/
com.foo.feature_v1.2.3.b
plugins/
com.foo_v1.2.3.b
7) delete dropins/com.foo.a.link
8) create a new link
/opt/eclipse-340-classic/dropins
com.foo.b.link :: path=/opt/mystuff_b
9) restart eclipse and mystuff is working as expected.
look at the software updates and addons page and that plugin is loaded and present with version 1.2.3.b
10) stop eclipse
11) delete directory /opt/mystuff_a/eclipse (the first version installed in step 2)
12) restart eclipse and none of com.foo extensions or properties pages are present
look at the software updates and addons page and it claims plugin com.foo is loaded and present with version 1.2.3.b
the workspace log contains errors about p2 not being able to find the com.foo_v1.2.3.a
Why does p2 still reference the old version?
How do I trigger p2 to reread / recache the content referenced in the dropins folder?
I'm stumped any help would be appreciated
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03286 seconds