Eclipse Community Forums: Equinox » p2 is not picking up new versions of plugins

Home » Eclipse Projects » Equinox » p2 is not picking up new versions of plugins

p2 is not picking up new versions of plugins [message #119151]

Wed, 08 October 2008 16:47

Eclipse User

We are struggling with converting our product build system to Ganymede /
Galileo. The biggest issue so far is that we are having trouble dealing
with patched plugins. While in Europa a plugin with newer version was
always picked up, this doesn't seem to be the case any more.

More details...

We have an ant-based build system that creates an "install" by unzipping
various eclipse distros and then adding our product plugins. The install
is then used for testing or packaged for distribution (as a unit).

Sometimes we run into bugs that we have to patch, while we wait for the
patch to make it's way into the project's codebase and then back to us, we
make a local patched build of the plugin in question (by exporting from
dev workspace). We then drop the plugin jar into the above install's
plugins directory. This used to be enough. The newer plugin version would
be picked up.

That doesn't work any more as of Ganymede. The p2 system seems to be
ignoring the new plugin. Any ideas how to get p2 to pickup the new plugin
version? Is there a way to force p2 to refresh its metadata? One of the
devs I work with is experimenting with hacking p2 metadata and is having
some degree of success with that, but I don't want to go that route if I
can help it.

Re: p2 is not picking up new versions of plugins [message #119190 is a reply to message #119151]

Thu, 09 October 2008 14:51

Eclipse User

Originally posted by: nospam_kowalskilee.gmail.com

Konstantin Komissarchik wrote:
> We are struggling with converting our product build system to Ganymede /
> Galileo. The biggest issue so far is that we are having trouble dealing
> with patched plugins. While in Europa a plugin with newer version was
> always picked up, this doesn't seem to be the case any more.
>
> More details...
>
> We have an ant-based build system that creates an "install" by unzipping
> various eclipse distros and then adding our product plugins. The install
> is then used for testing or packaged for distribution (as a unit).
> Sometimes we run into bugs that we have to patch, while we wait for the
> patch to make it's way into the project's codebase and then back to us,
> we make a local patched build of the plugin in question (by exporting
> from dev workspace). We then drop the plugin jar into the above
> install's plugins directory. This used to be enough. The newer plugin
> version would be picked up.
>
> That doesn't work any more as of Ganymede. The p2 system seems to be
> ignoring the new plugin. Any ideas how to get p2 to pickup the new
> plugin version? Is there a way to force p2 to refresh its metadata? One
> of the devs I work with is experimenting with hacking p2 metadata and is
> having some degree of success with that, but I don't want to go that
> route if I can help it.
>
>

My team is also struggling with p2 not picking up new plug-ins. We would
be interested in what you learn in terms of hacking the metadata.

Can the p2 team point to any documentation that describes the p2
metadata and how it is related to the plug-ins?

Thanks in advance,
Lee Anne

Re: p2 is not picking up new versions of plugins [message #119256 is a reply to message #119190]

Fri, 10 October 2008 10:37

Eclipse User

Konstantin and Anne,

Ganymede does not recognize plug-ins not installed (picked up through
update process). So you can not just put plug-ins into plugins folder. But
Ganymede has the concept of watched directories, in these folders you can
just add features/plug-ins and they will be recognized. The dropins
folder is the default watched directories.
For additional information refer to:
http://wiki.eclipse.org/Equinox_p2_Getting_Started

i hope it can help you

Gladyston

Re: p2 is not picking up new versions of plugins [message #119323 is a reply to message #119256]

Fri, 10 October 2008 15:14

Eclipse User

Originally posted by: nospam_kowalskilee.gmail.com

Hi Gladyston, thanks for the URL link.

I do know about the dropins folder, and am using it BUT p2 is not
picking up my plug-ins in the dropins folder. I would think it should,
right? :-)

That's why I'm asking for a reference to what metadata is cached and
where. If I knew that, I might be able to debug why my plug-ins in the
dropins folder are not being picked up.

Thanks,
Lee Anne

Gladyston wrote:
> Konstantin and Anne,
>
> Ganymede does not recognize plug-ins not installed (picked up through
> update process). So you can not just put plug-ins into plugins folder.
> But Ganymede has the concept of watched directories, in these folders
> you can just add features/plug-ins and they will be recognized. The
> dropins folder is the default watched directories. For additional
> information refer to: http://wiki.eclipse.org/Equinox_p2_Getting_Started
>
> i hope it can help you
>
> Gladyston
>

Re: p2 is not picking up new versions of plugins [message #119387 is a reply to message #119323]

Sun, 12 October 2008 03:10

Eclipse User

Originally posted by: ekkehard.gentz-software.de

Lee Anne schrieb:
> Hi Gladyston, thanks for the URL link.
>
> I do know about the dropins folder, and am using it BUT p2 is not
> picking up my plug-ins in the dropins folder. I would think it should,
> right? :-)
>
> That's why I'm asking for a reference to what metadata is cached and
> where. If I knew that, I might be able to debug why my plug-ins in the
> dropins folder are not being picked up.
>
> Thanks,
> Lee Anne
>
> Gladyston wrote:
>> Konstantin and Anne,
>>
>> Ganymede does not recognize plug-ins not installed (picked up
>> through update process). So you can not just put plug-ins into plugins
>> folder. But Ganymede has the concept of watched directories, in these
>> folders you can just add features/plug-ins and they will be
>> recognized. The dropins folder is the default watched directories.
>> For additional information refer to:
>> http://wiki.eclipse.org/Equinox_p2_Getting_Started
>>
>> i hope it can help you
>>
>> Gladyston
>>
I'm also using the dropins folder - if I put newer versions into the
dropins folder (per ex. Instatiations SWT Designer) I have to start once
with - clean and then the new plugins are available for ganymede

ekke

Re: p2 is not picking up new versions of plugins [message #119425 is a reply to message #119387]

Mon, 13 October 2008 09:16

Eclipse User

All,

I did some tests (not much), and for new plug-ins it always works, or
plug-ins that are not listed in some feature. but apparently if you
install a feature through Director you can not update its plug-ins just
adding new versions into the watched folder(because this way you will be
breaking the feature that owns the plug-in). I do not know if there is
another way to update these plug-ins (since they belong to an installed
feature) then through director.

P.S. Ekke: if you switch to another workspace this plug-in will be
recognized as well

Regards

Gladyston

Re: p2 is not picking up new versions of plugins [message #119529 is a reply to message #119425]

Mon, 13 October 2008 23:06

Eclipse User

Try a feature patch.

"Gladyston " <gladyston@gmail.com> wrote in message
news:6ef5895cdd2bddb474c210dbcf54a388$1@www.eclipse.org...
> All,
>
> I did some tests (not much), and for new plug-ins it always works, or
> plug-ins that are not listed in some feature. but apparently if you
> install a feature through Director you can not update its plug-ins just
> adding new versions into the watched folder(because this way you will be
> breaking the feature that owns the plug-in). I do not know if there is
> another way to update these plug-ins (since they belong to an installed
> feature) then through director.
>
>
> P.S. Ekke: if you switch to another workspace this plug-in will be
> recognized as well
>
> Regards
>
> Gladyston

Re: p2 is not picking up new versions of plugins [message #119554 is a reply to message #119529]

Tue, 14 October 2008 09:08

Eclipse User

Simon,

You just guess my suggestion :)
It works, but i was not able to go back to a previous configuration.
(there is no option to uninstall that patch)
Anyway, i just create following structure under dropins folder:

dropins
eclipse
features
<mypatch>
plugins
<plugin_with_fix>

Regards

Gladyston

Re: p2 is not picking up new versions of plugins [message #119686 is a reply to message #119554]

Thu, 16 October 2008 19:31

Eclipse User

I spent practically a whole day trying to get this to work. Nothing. I
have a patches feature that references the patched plugins. I dropped the
feature and plugins into the dropins directory. It is not getting picked
up. Features referencing new plugins are getting picked up. The patches
feature isn't. No messages in the log or anywhere else that I could find.

If I go use the update manager, I am able to install the patches feature
and then the plugins are getting picked up, but using update manager is
not an option for me. I have a build system that's trying to produce a kit
for people to download.

Any ideas, anyone, why it is so difficult to get this simple scenario to
work?

Re: p2 is not picking up new versions of plugins [message #119713 is a reply to message #119686]

Fri, 17 October 2008 13:17

Eclipse User

konstantin,

First, did you create following structure (and restart your product
with - clean option)?

dropins
eclipse
features
plugins

if so, are there any other plug-in or feature inside your product that
relies in the plug-in that you are patching? it is possible that some
plug-in depends on the old version of the plug-in that you are updating
via patch.

Regards

Gladyston

Re: p2 is not picking up new versions of plugins [message #119741 is a reply to message #119323]

Sat, 18 October 2008 10:18

Eclipse User

Lee Anne wrote:

> I do know about the dropins folder, and am using it BUT p2 is not
> picking up my plug-ins in the dropins folder. I would think it should,
> right? :-)

+1

I've tried to remove temporary Mylyn from dropins (to check my idea
that it has some bug). But when I've moved it again into dropins,
Eclipse does not see it anymore! No matter if I move it into new
directory, it just not detected.

Eclipse 3.5M2.

At the end I was forced to use Update manager to install it into
"plugins" folder. I hate this, because this makes hard to update to new
M build.

Re: p2 is not picking up new versions of plugins [message #119790 is a reply to message #119713]

Mon, 20 October 2008 11:28

Eclipse User

> First, did you create following structure (and restart your product
> with - clean option)?

> dropins
> eclipse
> features
> plugins

Yes, that's what I did.

> if so, are there any other plug-in or feature inside your product that
> relies in the plug-in that you are patching? it is possible that some
> plug-in depends on the old version of the plug-in that you are updating
> via patch.

No. All plugins use ranges. The only part of version that's changed is the
fourth segment. Version constraints is not the issue here. In fact, I can
install my patches feature manually via the update manager UI, in which
case the new versions of the plugins are getting picked up fine.

Re: p2 is not picking up new versions of plugins [message #119801 is a reply to message #119790]

Mon, 20 October 2008 12:59

Eclipse User

"Konstantin Komissarchik" <konstantin.komissarchik@oracle.com> wrote in
message news:d2eb7549e2a45900a7329e5b7b9b68a0$1@www.eclipse.org...
<<deleted some stuff>>

>> if so, are there any other plug-in or feature inside your product that
>> relies in the plug-in that you are patching? it is possible that some
>> plug-in depends on the old version of the plug-in that you are updating
>> via patch.
>
> No. All plugins use ranges. The only part of version that's changed is the
> fourth segment. Version constraints is not the issue here. In fact, I can
> install my patches feature manually via the update manager UI, in which
> case the new versions of the plugins are getting picked up fine.

The problem here is usually that some other feature (that you're not
patching) is referencing a specific version of a singleton bundle that you
are. You mention that you've verified your plugins but you might want to
grep through your features carefully too. If there really doesn't seem to be
any conflict then please open a bug.
-Simon

Previous Topic:	Upgrade from 3.4.0 to 3.4.1 fails
Next Topic:	org.eclipse.equinox.ds bundle not started with eclipse 3.5M2

Goto Forum:

-=] Back to Top [=-

Current Time: Sat May 10 05:47:49 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter