Christian, My understanding is that JPM indeed does something like this. In fact it has no physical storage of its own for libraries; it federates and enriches other repositories including Maven Central.
Hopefully Peter can clarify with some additional information. Regards, Neil On Sun, Nov 17, 2013 at 10:58 AM, Christian Schneider < [email protected]> wrote: > I would really like to see a repository with suitable OSGi meta data. > What I do not understand though is why many aproaches completely build up > their own repositories. > For example eclipse does this. They are publishing their p2 repositories > which contain just what is needed for the eclipse release + some small eco > system. The problem with these repos is > that you never find there all the artifacts you need for a project. On the > other hand they are not publishing to maven central. So it is very > difficult to use some of their artifacts outside OSGi and eclipse. > > Wouldnt it be better to simply deploy all bundles to maven central and > then just store the OSGi meta data in a separate repository? For example a > p2 repository could just point to the maven artifact coordinates > and only contains the meta data needed to search inside the repo. > Basically most of the meta data would not even be strictly necessary as it > is mostly contained in the manifests. So it is rather a cache. > So this would allow to create company repositories by just specifying > subsets of maven central without replicating all the artifacts. > > So how does jpm4j fare in this regards? Does it require its own repos or > would it work with artifacts from central? > > Regarding that many jars are still not valid bundles we should go on > encouraging the respective projects to create the meta data themselves. It > is just not manageable at large scale to create bundles externally for each > new jar version. > > Christian > > > Am 17.11.2013 11:44, schrieb Neil Bartlett: > > Actually I hope that with JPM4J integration (see jpm4j.org) we will be > able to do much better than Maven... > > As Ferry points out, the problem with using Maven central directly is > that most of its contents are not bundles. JPM is an effort to create a > global repository for OSGi bundles, however we are still working on this > integration. For now most organisations tend to use their own internal > bundle repositories. This may be some effort to set up initially but it has > advantages for the organisation in terms of control and governance, since > Maven central can be something like the Wild West! > > Regards > Neil > > > -- > > Christian Schneiderhttp://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
