We did the same for a commercial project. Started with a huge bundle build from all the jars and slowly took out parts either by making them separate bundles or by using pre-build bundles available.
Also if you want a quick start you can install Pax Runner, put all of this jars you need in a directory and from a terminal window you will just have to do: pax-run scan-dir:. --autoWrap This will start up latest Felix will all the jars from that directory (which are not already bundles) automatically converted to OSGi bundles. Magic :) Note tat the autoWrap is only available inside the 0.18.0-SNAPSHOT version of Pax Runner, which is not yet released, but yoy can use the snapshot version from OPS4J repo. On Thu, Mar 19, 2009 at 1:40 AM, Dmitry Skavish <[email protected]> wrote: >> Why is it you want to avoid setting the property? It wouldn't be too >> difficult to write a script to scan your JARs to define what the value >> should be. Further, you might be able to use BND to narrow the list down >> to only the packages you need to export. > > Yes, it is not that hard. I just feel it belongs to the build domain. The > source code which starts felix should use build's artifact in this case which > I am not really comfortable with. I guess this is ok if there are no other > options though. > > In fact I would probably prefer that to one huge bundle with all the third > party jars in it, although having one huge bundle would eventually force me > into breaking its content into individual bundles :) > > -- > Dmitry Skavish > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://www.codedragons.com - New Energy for Projects - Great People working on Great Projects at Great Places --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
