Inconsistency when resolving Target Platform Definitions targeting P2 sites at P2TargetUtils class [message #1256518] |
Tue, 25 February 2014 14:19 |
Victor Roldan Betancort Messages: 524 Registered: July 2009 |
Senior Member |
|
|
Hi everyone,
I've identified an inconsistency when having Target Platform Definitions which targets features in a P2 site. PDE indicates P2 a set of IRepository where it may find the artifacts to resolve. These repositories are those defined in the TP definition PLUS some implicit local repositories (basically, the local eclipse installation).
This is nice to optimize resolution of artifacts if locally available, but it may be inconvenient in some cases: for instance, if the bundle available in the specified remote P2 repository is customized and differs from the local one. As a consecuence, you won't get the code you are expecting.
The local resolution is triggered at P2TargetUtils class by:
/**
* return whether or not to use local artifact repositories when provisioning the target
*/
private boolean useAdditionalLocalArtifacts() {
// XXX consider using a preference here or another strategy if users are able to spec
// what local repos are to be considered.
return false;
}
As you see, its currently not possible to change this behavior.
So the questions are:
- As a workaround, is there any way to manipulate the list of local repositories? (I've read these are fetched from org.eclipse.equinox.p2.artifact.repository.prefs, but this file seems to be automatically populated at some point during startup)
- Any plans to introduce a preference to change the value returned by useAdditionalLocalArtifacts()? Are contributions in this regard welcome?
Best Regards,
Víctor Roldán.
|
|
|
Powered by
FUDForum. Page generated in 0.03717 seconds