[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [p2-dev] Metadata- and ArtifactRepository extensions.
- From: "Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
- Date: Fri, 6 Mar 2009 12:48:17 +0100
- Delivered-to: email@example.com
- Thread-index: AcmeUGRpMZgpxxTbTZ+sTeaAcMgk2AAAFd2w
- Thread-topic: [p2-dev] Metadata- and ArtifactRepository extensions.
Hi @ll :)
We implemented our own repos based on the 3.4 provisional API, these are great to expand and work as expected...
Looking at all the 3.5 changes we are looking forward to those provisionals becoming stable API, however, the repo API in particular seems to be stable and solid since it was crafted, some changes seem to have been necessary in 3.5 to add flags and change URLs to URIs but adapting to that is peanuts from an enhancer perspective...
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Henrik Lindberg
Sent: Friday, March 06, 2009 12:37 PM
To: P2 developer discussions
Subject: Re: [p2-dev] Metadata- and ArtifactRepository extensions.
Hi, p2 does not have an official API yet, so anything you use may have to change.
As you probably have seen packages are named "internal", and "internal.provisional" - the "provisional" packages constitutes the candidate API.
As focus has not been on API and how to extend things using these APIs there may be too many restrictions, or things you need may be missing.
So, no official API, and very little documentation. You just need to take a leap and get your hands dirty (to mix metaphors :) )
On Mar 6, 2009, at 12:20 PM, Fredrik Alströmer wrote:
> I got this crazy idea of wanting to look closer into creating a
> repository extension other than the simplemetadatarepository, however,
> all involved classes produce warnings about discouraged access, why is
> this? And what would I have to do to actually create an extension
> p2-dev mailing list
p2-dev mailing list