On Sun, Feb 22, 2015 at 10:42 PM, Fred Cooke <fred.co...@gmail.com> wrote: > I'd also love to hear that no one is trying to release 200 artifacts in a > single reactor.
At Wicket Stuff (https://github.com/wicketstuff) we do just that. It is a pain, but it is quite a lot less pain than trying to release each project by itself. > That makes no sense at all, to me. The chances are on a big > corporate project you've only changed <25% of them per top level release > anyway. So to run a top level MVN release against the entire tree would > produce 75% duplicate (by code, not number) artifacts. Or did I > misunderstand? You understand correctly, but in Wicket Stuff's particular case we assume that while not everything was modified, it is a much bigger benefit of having all version of all sub modules align, such that we can ensure that one particular version of Wicket works with one particular version of any Wicket Stuff project. For a release manager it is actually hard to figure out which projects should be released, releases of submodules linger long etc. The benefits for the community with regular, full releases are tremendous. No more trying to figure out which versions will work with your version of Wicket. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
