Re: [p2-dev] Problem while installing features with p2 core API s.

[Thomas Watson <tjwatson@xxxxxxxxxx>]

I'm not sure why this is happening, but it indicates that simple configurator is not using reference: URLs for installing the bundles so they end up getting copied into the osgi configuration cache.

Perhaps that will give you some hint as to why the p2 installation operation is doing that. See http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.simpleconfigurator/src/org/eclipse/equinox/internal/simpleconfigurator/ConfigApplier.java (the installBundles method). There is a configuration property (org.eclipse.equinox.simpleconfigurator.useReference), if this is set to "false" then the install process will not use reference: URLs to install. Another possibility is that the code does not think it is running on Equinox. This is checked by looking up the org.osgi.framework.vendor configuration property.

Tom



Pradeep Fernando ---08/26/2011 06:09:24 AM---Hi devs,

From:	Pradeep Fernando <pradeepfn@xxxxxxxxx>
To:	p2-dev@xxxxxxxxxxx
Date:	08/26/2011 06:09 AM
Subject:	[p2-dev] Problem while installing features with p2 core API s.

---

Hi devs,

I have a p2 enabled product. I was able to install features in to this
product using the p2-director application. The things worked just
fine. (this is provisioning external platform scenario).

Then I tried provisioning the  own platform using p2 core API
(provisioning the product itself). The things get installed, but the
problem is they get installed to cache area of the product. (to
configuration/org.eclipse.osgi directory).

I believe this is a fault in my end, most probably due to wrong use of
p2- API s.  Appreciate if anyone has clue/suggestion about this
behavior.

Thanks,
--Pradeep
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev