[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Querying remote p2 repositories
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Fri, 27 Jul 2012 15:23:41 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 ...which in OSGi 5 is part of the core specification.
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