Since there is already a thriving Maven repository collective, and most companies also have a repo of their
own in place (exactly for control and governance; I personally run Nexus), it would be unwise not use / tap
into this and instead try to setup an alternate collective. Maybe it would be possible to use the Maven
classifier to do this. Like there is "sourcecode" or "javadoc" we could also require all
OSGi artifacts to use a classifier "osgi". This would be the same jar but now with included OSGi
bnd file.
Talking about Nexus...
http://blog.sonatype.com/people/2009/07/nexus-pro-support-for-osgi-bundle-repositories
https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+P2+Repository+Plugin
On 2013-11-17 11:44, Neil Bartlett wrote:
Actually I hope that with JPM4J integration (see jpm4j.org <http://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
On Sun, Nov 17, 2013 at 9:11 AM, Ferry Huberts <[email protected]
<mailto:[email protected]>> wrote:
On 17/11/13 10:09, Daniel McGreal wrote:
Or just copy-dependencies goal?
we have something in development as a better solution to the Maven
'problem', but since none of us use it, it's not really high on our list of
things to do. help welcome...
On 17 Nov 2013, at 09:05, Ferry Huberts <[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
If you really want to use Maven (none of the bndtools developers do)
then you should look into the maven bundle plugin.
_______________________________________________
OSGi Developer Mail List
[email protected] <mailto:[email protected]>
https://mail.osgi.org/mailman/listinfo/osgi-dev
--
Ferry Huberts
_______________________________________________
OSGi Developer Mail List
[email protected] <mailto:[email protected]>
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
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
