apologies if this has gone to the wrong list. Let me know and I will
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
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
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 :-)
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
p2-dev mailing list