Sorry for top-posting, but I'm on my phone. Yeah, ideally, the plugin would translate perfectly from the Maven world into the Karaf world, but that just hasn't been my experience, so I just do it by hand and, for me, it's not a huge burden. Yes, there are times when things get screwed up, but it hasn't annoyed me enough at this point to sit down and write a patch. :) This is just my experience. Others may have been able to get better mileage out of the plugin. If so, I'm all for automation!
James On Mon, Feb 13, 2017 at 12:20 PM Thomas Vandahl <[email protected]> wrote: > Hi James, > > On 12.02.17 14:39, James Carman wrote: > > I always build my features by hand. It's just easier, IMHO. A few > > errors on the console telling you what's missing, and you're off to the > > races. You can also try using PAX exam to test your features, but I've > > found that to be more trouble than it's worth (it always chooses to fail > > when I'm trying to do something important, like cut a release). > > You are probably right, but something inside me refuses to accept that > if my dependency management are good enough for Maven they still are not > good enough for Karaf. This manual editing adds a possibility for failure. > > Bye, Thomas >
