| How to define "dynamic" target definitions? [message #606471] |
Mon, 16 August 2010 16:50  |
 Kaloyan Raev
Messages: 201
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi,
I am building an OSGi dev environment where the Target Platform is a set of Eclipse Runtime bundles.
I'd like to make the installation of the Target Platform as easy as possible for users. Sure, my choice is to install it from a p2 repository. I even go one step further and register my p2 repository as a Target Definition Template (using the org.eclipse.pde.core.targets extension point). This way my users don't need to remember the URL of the p2 repository, but just select the template from the drop-down list.
All works fine, but I noticed that the target definition file, that I registered as a template, has references to a fixed set of installable units. By "fixed" I mean that the definition references an *exact* name and *exact* version.
This is problem for me, because the p2 repository resides on a build server and is updated every night. This nightly update also increments the qualifier of the version. It is also possible that a feature name changes or a features is added/deleted. This means that on the next day the target definition, that I registered as a template, will be broken.
Now, my question. Is it possible to define the target definition in a way that it means: "Go to this p2 repository and take everything you find" ?
Thanks,
Kaloyan
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03285 seconds