[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 11:45:33 -0500
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acl3+Yo6jdo2YTkmQpSL2R98fMy9nAAACQAA
- Thread-topic: [p2-dev] plugins folder provisioning
So reconciler.dropins handles "plugins" folder provisioning
as well as "dropins" folder?
The bundle is org.eclipse.equinox.p2.reconciler.dropins.
In a nutshell
what it does is try to install everything it finds "OPTIONALLY".
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
Warren_Paul---01/16/2009 11:04:10 AM---Hi Folks,
01/16/2009 11:04 AM
[p2-dev] plugins folder
As per this paragraph on the
getting started wiki page:-
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?