On Mon, Feb 28, 2011 at 19:36, karafman <[email protected]> wrote: > We've been talking in IRC about new features we could add to Karaf to make it > more accessable to development teams who don't know much about OSGi. Things > that would decrease the learning curve. This thread's intent is to gather > suggestions, and to give feedback to them. > > To start the thread: > > 1) Inspect each bundle on deployment for the MANIFEST.MF header > "Bundle-ManifestVersion", and then automatically wrap ones missing that > header.
The wrap deployer does that if you drop a jar in the deploy folder. > 2) Have Karaf look at each .jar or .ear being deployed for a > "Bundle-Version" in its Manifest.MF file, and if it doesn't have it, look > for a ./lib directory, wrapping and deploying everything in that directory, > then removing it from the original .jar file, then wrapping the original > .jar file, and finally deploying and starting the original. This wouldn't > configure services, but it would provide a strong starting point for teams > moving from JEE to Karaf. Wouldn't it be easier to use a Bundle-ClassPath instead ? That's what is done when you drop a war in the deploy folder. > 3) Have karaf look in META-INF/spring and OSGI-INF for all xml files, and > then automatically add any packages referenced there to the Import-Package > portion of the MANIFEST.MF file. This is probably a bnd change, but still > would be a nice-to-have. That is be done already either using the maven-bundle-plugin or the blueprint/spring deployer from the deploy folder. > > ----- > Karafman > Slayer of the JEE > Pounder of the Perl Programmer > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Suggested-3-x-x-functionality-tp2597220p2597220.html > Sent from the Karaf - Dev mailing list archive at Nabble.com. > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
