Peter, Just so you know, the karaf-maven-plugin development is quite a bit in flux. I started doing a lot of work on it, but it was said that it was easy enough to just develop features descriptors by hand and that plugin development wasn't essential. You can refer to the thread if you like, but I'm really not happy with where the plugin is or the output that it generates.
I'm saying this so you can avoid a lot of frustration with it. I did a lot of work on it and still don't find it usable. Until it gets fixed (and I'm very eager to get it fixed because I disagree with the statements about the plugin being unimportant), the best thing to do is to put your features descriptor in your resources folder, make sure resource filtering is enabled, then use build-helper-maven-plugin to attach the feature artifact to the build from the target/classes folder so you get what you expect as the final deployed artifact. I'm sure this will eventually get fixed, and I put in all the unit tests so that there could be a community discussion on what features should and should not be supported, but it's just not there yet. Cheers, Brian On Aug 23, 2012, at 2:52 PM, peterg <[email protected]> wrote: > I've opened a Jira issue to track this issue: > https://issues.apache.org/jira/browse/KARAF-1764. > > best regards, Peter > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/karaf-maven-plugin-started-producing-features-with-a-new-namespace-incompatible-with-Karaf-2-2-9-tp4025746p4025797.html > Sent from the Karaf - User mailing list archive at Nabble.com.
