Community
Participate
Working Groups
Currently the user is allowed to specify a System property - org.eclipse.equinox.p2.reconciler.dropins.directory - which points to a location that we will treat as a drop-ins folder. We have had cases where it would be useful to allow the user to specify multiple locations. We talked about allowing the property to hold a list of folders but this is hard because the framework currently does not support cascaded System property merging and if we were to change this, changes would have to occur at many levels. (exe, launcher jar, etc) Tom and I talked briefly about somehow leveraging the links files to do this. And John suggested allowing for variable substitution in the links files, something like: path=%company.web.dropins%/web-group and when we process it, we would look for a "company.web.dropins" System property to do the substitution. This would allow the user or product to have multiple link files and drop-ins folders if they wanted.
if done for 3.7, is this something that could be ported back to 3.6.2 or would it be considered new API?
Depending on the complexity of the implementation, this could potentially be back-ported.
Created attachment 186313 [details] patch First cut at a patch. It allows variable substitution for paths in .link files as well as in the "org.eclipse.equinox.p2.reconciler.dropins.directory" system property. Variables appear in the form: %key% Values are taken from the system properties for the running instance. (BundleContext.getProperty(key)).
Released to HEAD.
