Hi, These are closely related to each other.
If it is to be something that only ever produces a JAR, then removing the -bundle sounds fine and you'd switch to a <packaging>osgi-bundle</packaging> technique, in which case install and deploy will just work, and will involve compilation, etc. If sticking with the -bundle notation so that you can produce both a regular and bundled version of a JAR, then project.addAttachedArtifact(...) should be used to enabled install/deploy support. Both the bundle and the original JAR will be pushed together. The part that does the osgi modifications should be put into the lifecycle (probably part of the resources or packaging phases), allowing compilation and installation all to happen in one step. Hope this helps, and I'll try and spend some more time reviewing the plugin soon now that the m2 beta is out. Cheers, Brett On 9/19/05, Enrique Rodriguez <[EMAIL PROTECTED]> wrote: > > Some feedback on the Felix M2 Plugin: > > 1) I don't like having my bundles named with the '-bundle' appended. I > am used to bundles being jars with nothing in the naming specifying > that. Since the manifest attributes of normal jars and osgi jars don't > conflict, there is no harm generating a single jar that is usable as > both a non-osgi jar and a bundle. > > 2) I couldn't figure out how to 'install' or 'deploy'. Are these > features in there yet? > > 3) I would prefer to compile and bundle in a single step. With the > maven-osgi-bundle my most-used goal is 'maven -o clean osgi:install' > which would clean, compile, and install my bundle to my local repo. I > then install or update in the framework directly out of the maven repo. > > Of course if you note any of these issues as bugs/new features I'll be > sure to add them to JIRA. I was pretty easily able to get started with > M2 and the Felix M2 Plugin and compile and bundle one of my projects. I > think 'install' support is the main showstopper for me. > > Enrique >
