Greetings, we are investigating alternatives to building osgi bundles (and resolving/retrieving bundles for ease of copying to virgo-tomcat/repository/usr) in an "ivy-first" approach.
I found the following docs which encourage me and I'd love to get started with this and help if need be. According to http://ant.apache.org/ivy/history/trunk/osgi.html So with a standard ivy.xml, you can express some dependency on some OSGi bundle and every of their trasitive dependencies will be resolved. You can also declare in your ivy.xml some OSGi dependency, like a Require-Bundle, an Import-Package or an Import-Service, miming an OSGi MANIFEST.MF. According to http://ant.apache.org/ivy/history/trunk/osgi/standard-osgi.html In oder to produce OSGi metadata of suffient quality and to avoid maintaining them manually, the bnd <http://www.aqute.biz/Code/Bnd> tool will be used. The approach taken is then an "Ivy file first" approach. The dependencies will be specified in the ivy.xml file, the MANIFEST.MF being generated from the computed classpath. Then, on the other hand I see this support for manifest-first docs: According to http://ant.apache.org/ivy/history/trunk/osgi/osgi-mapping.html there is early experimental work to map osgi manifest first to generated ivy.xml Also http://ant.apache.org/ivy/history/trunk/use/convertmanifest.html since 2.3 Convert a MANIFEST.MF into an ivy.ml file Sigh.. no mention of any sort of genbnd or genmanifest ant tasks Can someone clarify encourage me and shed a timeline for if/when this might be able to be used? Can I getstarted now? Do I have to build ltest from src? Also the http://ant.apache.org/ivy/history/trunk/osgi/standard-osgi.html quick-setup link to download the bnd file seems broken (no content) Thanks, Richard
