Hi Klaus,
One way to go here would be to define/create a small set of OSGi service
interfaces that provide access to serializable (and perhaps
customized/simplified) representations of p2 metadata. You could design
the service interfaces to be specific to Maven/Tycho...or
indifferent/abstract from the build. I've done this myself for some
kinds of p2 metadata (installable units and feature groups).
Then, it would be/is fairly simple to use these OSGi service
interface(s) remotely...and/or locally...via the OSGi remote services
standard [1][2]...which in OSGi 5 is part of the core specification.
FWIW.
Scott
[1] http://www.osgi.org/Specifications/HomePage
[2] http://wiki.eclipse.org/ECF#OSGi_Remote_Services
On 7/27/2012 6:42 AM, Kopecz, Klaus wrote:
I'm looking for a simple way to query a remote p2 repository (simple and/or composite).
The p2-API documentation at help.eclipse.org indicates that this can be done in the
context of having a ProvisioningAgent representing the "p2 area" of an Eclipse
installation.
My context is different. I want to query a p2 repository in the context of a Maven/Tycho
build and therefore cannot refer to any profile or "p2 area". Therefore, I'm
looking for some basic p2 infrastructure which can read (or even query) the metadata of a
remote repository basically by providing the URL. While I could write some stuff to read
and analyze a remote content.xml file, things get more complex if I want to abstract from
having simple and/or composite repositories which differ in their file layouts and
decomposition into multiple metadata sources. Having something which could do this
abstraction for me would be helpful.
Thanks for any suggestions ...
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
