Gang, I have had a quick look at Peter Kriens' BND program.
http://www.aqute.biz/php/tools/bnd.php I like what I see, and propose that we provide a Maven plugin around it, and possibly deprecate the current one. People who wants to maintain the current is of course free to do so, but sooner or later the one at Felix should be the prefer one, if you want to go down that route. Back to Peter's work; He writes; <quote> Introduction The bnd tool helps you create and diagnose bundles. The key functions are: * Show the manifest and JAR contents of a bundle * Wrap a JAR so that it becomes a bundle * Create a Bundle from a specification and a class path * Verify the valdity of the manifest entries The tool is capabable of acting as: * Command line tool * Eclipse plugin * Ant Task * Maven Plugin </quote> Instead of embedding everything inside the POM, he has been smart enough to keep the meta-info external. +----------------+ +--------------+ +----------+ | BND definition | --> | BND compiler | --> | Manifest | | file | +--------------+ +----------+ +----------------+ | | (and/or) +------------+ +-----------> | Bundle Jar | +------------+ This fact makes it a lot easier to integrate into build systems and IDEs. My suggestion is that we make a new Maven OSGi plugin, that takes BND formats, calls the BND system to generate the Jar. We could also implement a back-compatibility feature, where the current plugin format results in generation of a BND file, which is then processed. It will also allow me to spice up the IDEA OSGi plugin I am working on, to store the data in BND file, instead of trying to resolve the Maven POM into something meaningful. WDYT? Cheers Niclas _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
