Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » P2 and link files error
P2 and link files error [message #113242] Thu, 03 July 2008 17:12 Go to next message
Eclipse UserFriend
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
Re: P2 and link files error [message #113308 is a reply to message #113242] Fri, 04 July 2008 06:08 Go to previous messageGo to next message
Zviki Cohen is currently offline Zviki CohenFriend
Messages: 25
Registered: July 2009
Junior Member
See the following bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=232094

Currently, removing link files does not uninstall the plug-ins. My guess
is that you had both locations active and the newer version was used on
the second run.
Re: P2 and link files error [message #113623 is a reply to message #113242] Wed, 09 July 2008 03:04 Go to previous message
Pascal Rapicault is currently offline Pascal RapicaultFriend
Messages: 333
Registered: July 2009
Location: Ottawa
Senior Member
Does -clean help?

"Mark Russell" <fireresq@embarqmail.com> wrote in message
news:g4j1a8$98b$1@build.eclipse.org...
> 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
>
Previous Topic:p2: generate metadata over networked drive
Next Topic:Equinox porting
Goto Forum:
  


Current Time: Fri Apr 26 19:32:10 GMT 2024

Powered by FUDForum. Page generated in 0.03286 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top