[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] FW: P2 Profile Questions
The overall idea of creating what you need (metadata and profile) as part of the build is good and I believe this is the path to follow.
What I like about this is that by the same token that the eclipse you download today result from a provisioning operation, you can then see the WAR you ship resulting itself from a provisioning operation and it makes things consistent.
I think that what made this whole experience weird for you is deficiencies in our tooling / metadata generation tooling that is still very driven of complete products in a standard eclipse shape. This is something that is being improved as we speak and we are looking at ways to generate metadata from source information and not require the product or whatever you build to be in its final shape.
We are mostly focused on RCP product builds, so please make sure to follow what is going there to make sure your scenario is addressed if possible.
One last thing, please try to not use the "dropins" folder to provision... this is the worst way. Try invoking the director directly, this will be much cleaner.
Warren_Paul---19/11/2008 01:00:44 PM---Hi Folks,
19/11/2008 01:00 PM
[p2-dev] FW: P2 Profile Questions
Firstly, apologies if this has gone to the wrong list. Let me know and I will repost immediately.
I'm considering refactoring the webapp quickstart code and submitting back to the community. To that end I've started a discussion page here:-
Before I do this however I'd like to check that I understand p2 and that this is, in fact, a required course of action for me.
My understanding is that any 3.4 equinox application wishing to use p2 (as well as including the p2 bundles) must establish a valid p2 profile around the initial "bootstrap" application. Otherwise p2 wont provision at all or wont provision properly. There are at least a couple of ways of doing this:-
1. Establish a p2 profile for the bootstrap application during the nightly build and make it part of the application
2. Establish a p2 profile the first time the application is started (the webapp quickstart approach)
To date I have attempted to go the first route. Briefly, I have a version of the servlet bridge that I've modified to use a release version of the ganymede codeline. I've manually updated the set of bundles to include p2, the simpleconfigurator and simpleconfigurator.manipulator. I created a basic profile for this installation by using the admin UI and using it to provision a feature that contained all the same bundles as my initial installation. I copied this profile into my application. I then found that I had to add all the "tooling.*" installable units to this profile as they were missing and this was causing provisioning issues.
After these steps I've had some success provisioning other features and bundles from updates site and by dropping them into the "dropins" folder.
So, I was happy I got it working :-)
But it seems a bit hokey process to me. Perhaps I am doing it wrong? Or perhaps the webapp quickstart is actually the right way of doing this? Or perhaps they are two ways of achieving the same goal.
Would love to hear anyone thoughts on the subject.
p2-dev mailing list