When you say “move … into the bnd build” do you mean check out the source from the Apache SCM and build snapshots as part of bndtools CI, or are you talking about moving/copying code into the bndtools SCM?
Also note that while you would be free to do your own releases using a different groupId, anything released under the Apache groupId would need to go through the Apache release process. On 28 Aug 2014, at 15:56, Peter Kriens <[email protected]> wrote: > In the bnd(tools) group We currently are discussing the maven bundle plugin. > The idea was raised to build this plugin during the normal continuous > integration so we can keep the version current. We are already building > another maven plugin in our build and releasing it so it should be quite > straightforward for us. This would have the benefit that whenever we release > a candidate or a final version we would put it in maven central as quickly as > possible. From a logical point of view it seems to make sense to move the > Apache Felix Bundle plugin into the bnd build since it is so closely coupled > to bnd. > > That said, logical is sometimes to rational (and there might be drawbacks we > have not considered). Obviously we do not want to do anything that goes > against the wishes of the Apache Felix group, we value this group way too > highly to offend it so if the feelings here are not abundantly positive then > we won't even look in that direction. > > Are there any drawbacks? How does this group feel about this? > > Kind regards, > > Peter Kriens >
