I'm -0 on this one. However, I think we can do this and see where it takes us, at least let it work for the 1.3-beta1-incubating release and see if/how it improves the release.
In the very least it cleans up our pom's to a great extend. I only want one thing changed: the root pom should have the same version as the rest of the projects, because the dependencies and plugins are release specific (i.e. bound to the era of the release). I don't expect the root pom to live its own live, at least not with dependencies and plugin configuration inside. -1 on renaming the branch: it seems too soon to me. We decided on this naming to get rid of what our 1.x and 2.x streams were. As we are going to vote on the future of trunk, I'd say don't change it just now but wait with any renaming change until we sorted that out. Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
