For our software projects, we use OSGi -- a dynamic module system for java. If you're not familiar with it, OSGi allows you to attach some extra meta-information to the Manifest of a jar that describes dependency information of the jar as well as which packages (and versions) the jar contains. This augmented jar in OSGi-speak is a bundle. (There is a whole lot more to OSGi as well).
Because we wanted to use the LTK-Java inside one of our projects, we needed to make a bundle out of the jar. We put it (along with "bundlified" versions of its runtime dependencies) up on our public svn in case anyone is interested to look/play around with. You can find it at https://svn.rifidi.org/svn/rep-external/llrp/ltk-bundle-jars/ I know alot of projects now are releasing their java projects as OSGi bundles. Because making a jar OSGi compliant is simply adding some extra information to the Manifest (programs not using OSGi will never know the difference), it may be something to think about for the LTK-Java project as well. We have built up quite a bit of OSGi knowledge and would be willing to help out if anyone is interested. Thanks, Kyle Neumeier Pramari, LLC ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
