I also have a maven centric build. All the obr features and also the new
repository spec sound really promising but I till now we use the much
simpler aproach with the maven bundle plugin.
There you use the maven dependencies for the compile time classpath and
let the maven bundle plugin create the manifest. This works quite well
for most cases.
The downside is of course that you e.g. can not see in eclipse if one
bundle accesses private packages of another bundle. In practice this is
not such a big problem though. For me the main point for staying with
the maven build instead of e.g. bnddtools is that I need a lot of open
source dependencies and maven is the easiest way to fetch them.
For some examples how this works you can take a look at my Apache Karaf
tutorials or the karaf build itself. Most of the apache projects that
are OSGi ready (like Aries, Camel, CXF or ActiveMQ) use this kind of
build too.
http://www.liquid-reality.de/display/liquid/Karaf+Tutorials
https://github.com/apache/karaf
Christian
Am 17.11.2013 12:15, schrieb Tom Eugelink:
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
--
Christian Schneider
http://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
