Re: [p2-dev] Creating the p2 profile manually

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Your current problem is rooted in the fact that your initial distribution is not resulting from a provisioning operation. As such, there is no p2 profile no artifacts.xml, etc. but there is probably other aspects of the system that are misconfigured.
For the eclipse SDK, or the EPP packages, this problem is solved by creating the initial distribution by invoking the p2 director. If your platform resemble an eclipse installation, then you should be able to do the same (maybe starting from a product file to ease the task) and then avoid many other subtle problems

Otherwise the approach of spoofing up a profile should work. I have created an example for something similar in the incubator (in the RT repo org.eclipse.equinox/incubator/p2/bundles/org.eclipse.equinox.p2.afterthefact). It creates a profile for all the bundles in your system, but it does not properly set up the inclusion flag when creating the original profile nor does it try to manage the artifacts (for example the IU being generated does not have an artifact key).

I think the problem you are encountering with the feature.xml is probably related to the absence of a proper platform.xml (wild guess). If you don't care about having the feature.xml on disk, then simply don't install them since all the interesting metadata that p2 needs is in the IU whose name ends with .feature.group. To not have the feature.xml be installed, set the org.eclipse.update.install.features profile property to false when you create it the first time.

HTH

PaScaL


Re: [p2-dev] Creating the p2 profile manually

Re: [p2-dev] Creating the p2 profile manually

Saminda Wijeratne

to:

P2 developer discussions

06/23/2009 08:01 PM

Sent by:

p2-dev-bounces@xxxxxxxxxxx

Please respond to P2 developer discussions

---

Problem in this method is that the p2 does not support uninstallation of such methods. Which is y we need an alternative. btw is there any plan to add the uninstallation of features in feature folder through the p2 conosle?

Any other ways which we can solve the original problem?

Thanks,
Saminda

On Tue, Jun 23, 2009 at 6:35 PM, Saminda Wijeratne <samindaw@xxxxxxxx> wrote:

We are using p2 as the provisioning system for wso2 carbon. When creating carbon distributions, bundles related to some features are already present by default. We want to tell the p2 that to consider such features as already installed features in the distribution. As we understoof for that to happen the related information should be included in the p2 profile and the artifact.xml. We also have the feature jar file prior to creating the carbon distributions.

One way we thought of is to rather than creating the profile and artifact.xml manually we can put the feature jar in the features folder in which case p2 should pick it up and install. However for some reason it is not being picked up. Turns out i needed to have "...config.dir/org.eclipse.update/platform.xml" in place.

Thank you,
Saminda


On Tue, Jun 23, 2009 at 5:29 PM, Henrik Lindberg <henrik.lindberg@xxxxxxxxxxxxxx> wrote:
What is it you are trying to do?

In general - you should use p2 to install things and this will create/update the profile. You can run the director or p2-installer to do this. If you have really special needs you can create your own special installer. Hacking the files directly is not recommended.

Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx




On Jun 23, 2009, at 8:21 AM, Saminda Wijeratne wrote:

Hi,

Is it possible to create a p2 profile and the artifact.xml manually for a given set of features? Is there some spec publicly available which we can follow?

Looking at an existing profile the feature information seems to be taken from the content.xml of that particular repo which the feature is installed from. but the iusProperties tag is new.

Thank you,
Saminda

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

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

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