Looking at the OSGi-enabled Lift poms, I find it curious that the M.O. for building bundles looks like a two-step:
1) Build a bundle with maven-bundle-plugin 2) Dig out the manifest and use it in the jar This works ok, but given my experience with Maven, it seems to be a case of challenging destiny (Norwegian idiom, sorry); I can vividly picture future Mavenisms shuffling the order of plugins somehow, wreaking silent havoc. My preferred approach would be to change the packaging of the pom from jar to bundle. From what I can tell, the plugin simply binds to this packaging type (or something), and does the same job. I tried this to bundle-wrap the Mapper and the Widgets (trying to deploy my app in Felix + Jetty), and it works fine. Should be faster, too. Unless, of course, I'm missing something here? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
