[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [p2-dev] plugins folder provisioning
- From: Warren_Paul@xxxxxxx
- Date: Fri, 16 Jan 2009 16:08:51 -0500
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acl4AgGzMFbzb0BQQDuC6X6nyVQQAQADYV+w
- Thread-topic: [p2-dev] plugins folder provisioning
Got it. Many thanks Simon.
Points noted about dropins & back compat.
One interesting use case that I think will need supporting
going forwards (at least medium term) is how all this meshes together with
servlet bridge type implementations.
Whilst I definitely agree that a servlet bridge osgi
instance can be managed via the director app or some web-based version
of eclipse's software updates whilst in production.
Developer use cases may, I think, be slightly different. They
would seem to be more focussed on a changing system manifest over time rather
than on any onward provisioning the user or an administrator might
do. A developer developing within the context of a servlet bridge
(i.e. a webapp) will need some sort of workspace (dropins?) where he can develop
his bundles and he will expect to be able to drop new bundles into "plugins" as
dependencies from his bundles are discovered and added during the course of his
At least that is the medium term use case that I see.
Not sure how this will play out longer term as osgi matures as a
server-side technology, possibly as a first class citizen.
Those are some thoughts anyway. Would love to hear
Once again many thanks for the quick response
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of
Sent: 16 January 2009 17:44
To: P2 developer
Subject: RE: [p2-dev] plugins folder
Yes that's right. The same mechanism is also used for .link files and cases
where someone is messing with platform.xml.
One thing to keep in mind is that
the dropins support is there primarily to ensure we have a backwards
compatibility story. As an install gets more complex you really should use the
"director" (either in-process with the UI or out of process with the director
>From what I've seen, without it your install is going to be
increasingly brittle in the face of anything else getting
Warren_Paul---01/16/2009 11:47:52 AM---Hi Simon,
01/16/2009 11:47 AM
RE: [p2-dev] plugins folder
So reconciler.dropins handles
"plugins" folder provisioning as well as "dropins" folder?
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Kaegi
Sent: 16 January 2009 16:43
To: P2 developer
Re: [p2-dev] plugins folder provisioning
The bundle is
In a nutshell what it does is
try to install everything it finds "OPTIONALLY".
What that means is that if
anything else is already installed that conflicts with the new thing the
"optional" bundle/feature will not get installed.
What this amounts to is
that In many cases the "version increment" use-case will fail without a matching
feature patch. This is because the feature will typically reference an exact
version of a bundle and without the patch the net result would be an invalid
Warren_Paul---01/16/2009 11:04:10 AM---Hi Folks,
01/16/2009 11:04 AM
[p2-dev] plugins folder provisioning
As per this paragraph on the getting started wiki page:-
"The new dropins folder is where
you can drop in extra plug-ins if you don't want to use the p2 user interface.
See the dropins section for more details. For backwards
compatibility, p2 will also detect extra plug-ins dropped into the
plugins directory, and install any discovered bundles
into the system."
it seems eclipse
will still pick up new plugins dropped into the plugins folder. I'd like to
understand the extent of this implementation - for example will it also detect
version increments from "plugins"?
Can someone point me at the bundle that is
responsible for handling provisioning of the "plugins" folder?