| RE: [p2-dev] plugins folder provisioning |
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 app).
>From what I've seen, without it your install is going to be increasingly brittle in the face of anything else getting installed.
-Simon
Warren_Paul---01/16/2009 11:47:52 AM---Hi Simon,
From: | Warren_Paul@xxxxxxx |
To: | <p2-dev@xxxxxxxxxxx> |
Date: | 01/16/2009 11:47 AM |
Subject: | RE: [p2-dev] plugins folder provisioning |
The bundle is org.eclipse.equinox.p2.reconciler.dropins.
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 install.
-Simon.
Warren_Paul---01/16/2009 11:04:10 AM---Hi Folks,
From: | Warren_Paul@xxxxxxx |
To: | <p2-dev@xxxxxxxxxxx> |
Date: | 01/16/2009 11:04 AM |
Subject: | [p2-dev] plugins folder provisioning |
