Eclipse Community Forums: P2 » legacy sites and "new" updatemanager

Home » Eclipse Projects » P2 » legacy sites and "new" updatemanager(plugins not unpacked?)

legacy sites and "new" updatemanager [message #656417]

Fri, 25 February 2011 09:23

Eclipse User

I have an issue with a couple of external plugins.

I have downloaded an external feature that used an legacy site.xml to distrubite updates.

I did this via the b3 aggregator and published them internally and naturally i then got the p2 metadata for these.

When i install this feature via the old legacy site with site.xml all is fine, certain plugins is unpacked.

But when i try to install it via the new built p2 site i did with the b3 aggregator it fails to unpack plugins ( it doesn't say anything no errors etc) in my eclipse installation, and since the plugins need to be unpacked they don't work.

is there any logging i can turn on to see why it does not unpack some plugins? i know that this is supposedly to be listed in the feature.xml with unpack=true or in the manifest.mf file / plugin. The weird thing is that it unpacks them when i install them from the legacy site but not from an p2 site..whats going on?

This is in Eclipse 3.6.1 on windows XP. i can recreate the issue with an built updatsite i got, bug?

Help?!

best regards

David

edited - spelling

[Updated on: Fri, 25 February 2011 09:24] by Moderator

Re: legacy sites and "new" updatemanager [message #656497 is a reply to message #656417]

Fri, 25 February 2011 17:11

Eclipse User

Sounds like an issue with the b3 aggregator. If you have repeatable case,
please log an issue. (or convince the publisher of the site to publish p2
directly).
- henrik

David <david.samuelsson.se@gmail.com> wrote:
> I have an issue with a couple of external plugins.
>
> I have downloaded an external feature that used an legacy site.xml to distrubite updates.
>
> I did this via the b3 aggreagtor and published them internally and
> naturally i then got the p2 metadata for these.
>
> When i install this feature via the old legacy site with site.xml all is
> fine, certain plugins is unpacked.
> But when i try to install it via the new built p2 site i did with the b3
> aggregator it fails to unpack plugins ( it doesnt say anything no errors
> etc) in my eclipse installation, and since the plugins need to be unpacked they don't work.
>
> is there any logging i can turn on to see why it does not unpack some
> plugins? i know that this is supposedly to be listed in the feature.xml
> with unpack=true or in the manifest.mf file / plugin. The weird thing is
> that it unpack them when i install them from the legacy site but not from
> an p2 site..whats going on?
>
> This is in Eclipse 3.6.1 on windows XP. i can recreate the issue with an
> built updatsite i got, bug?
>
> Help?!
>
> best regards
>
> David

--
- henrik

Previous Topic:	building p2 headless without a product/application
Next Topic:	Create eclipse feature from target platform (Include all Environments )

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 11:44:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter