The main reason is that if you want to generate the P2 metadata files, and manage a P2 repository, the simplest way is to embed the P2 implementation from Eclipse which of course, runs into an OSGI container.
Regards Jeff On Thu, Oct 18, 2012 at 3:20 PM, Olivier Lamy <[email protected]> wrote: > 2012/10/18 Jeff MAURY <[email protected]>: > > Basically, you need to support the following features: > > > > - proxy > not so complicated > > - aggregation (ie groups) > not so complicated > > - automatic transformation of Maven repo in a P2 one: Nexus does it by > > supporting the notion of repo listener, which is notified each time a > new > > artifact is stored in the Maven repo, the listener looks if this is > an OSGI > > artifact and add it to the associated P2 repository. This is really > > helpfull when you need to use in an Eclipse plugin (with Tycho) a > Maven > > produced artifact OSGIfied with the Maven Felix BND plugin. The P2 > repo is > > stored under the Maven repo (in a hidden .xxx directory) > > > > In order to do that, we need to run all P2 stuff in an OSGI container so > it > > would be simple if Archiva is OSGI based, a little bit more complex if we > > need to launch an OSGI framework. But it has some impact on Archiva > plugin > > packaging > Why running all P2 stuff for Archiva in an OSGI container ? > If I understand correctly it's just a matter of detect osgi metadatas > in deployed jars (i.e. parsing MANIFEST.MF) ? > > For sure an osgi container could ease plugin stuff (dynamic loading > etc..) but that need some work :-) > > > > > Jeff > > > > > > On Thu, Oct 18, 2012 at 12:03 AM, Olivier Lamy <[email protected]> wrote: > > > >> 2012/10/17 Jeff MAURY <[email protected]>: > >> > Hello, > >> > > >> > having a lot of problems with Nexus OSS P2 support, I'm wondering if > >> there > >> > is any work done or planned in order to support P2 repos in Archiva ? > >> > Also, is there a documentation about the internal architecture and > >> > extension points ? > >> Currently no extensions point except writing a consumer which won't > >> really help in your case. > >> It's on my TODO list to review a bit the architecture to be able to > >> write your own repository type. > >> This need some refactoring as in some parts we are very maven centric > :-). > >> > >> BTW as I'm noob in p2 I will ask support from people with more > >> knowledge on this part. > >> I don't know if p2 support is just a kind of proxy which cache file in > >> the mrm or if this need to do some deps resolution. > >> > >> > >> > > >> > Thanks > >> > Jeff > >> > > >> > -- > >> > Jeff MAURY > >> > > >> > > >> > "Legacy code" often differs from its suggested alternative by actually > >> > working and scaling. > >> > - Bjarne Stroustrup > >> > > >> > http://www.jeffmaury.com > >> > http://riadiscuss.jeffmaury.com > >> > http://www.twitter.com/jeffmaury > >> > >> > >> > >> -- > >> Olivier Lamy > >> Talend: http://coders.talend.com > >> http://twitter.com/olamy | http://linkedin.com/in/olamy > >> > > > > > > > > -- > > Jeff MAURY > > > > > > "Legacy code" often differs from its suggested alternative by actually > > working and scaling. > > - Bjarne Stroustrup > > > > http://www.jeffmaury.com > > http://riadiscuss.jeffmaury.com > > http://www.twitter.com/jeffmaury > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
