The ideas/requests/demands just keep coming... With a clean slate for IB3 I want to propose a few things. I have been using Maven2 for a while now and even use it in my day to day development. My first suggestion is to lay out the new source tree to map to the maven2 style of convention over configuration. Even if we choose not to use Maven as the build/deployment process it is the most logical and thought out hierarchy that I have seen.
On the topic of Maven2 I would like to nominate is as the build/deployment process. Maven2 offers so many pre-built plugins for many useful things from coverage reports to unit test results. If there is something that Maven2 does not have I am sure we could write a quick plugin to get it done. I have also been using a new CI tool with Maven2 ( https://hudson.dev.java.net/ ). Insanely easy to install and configure. Just reads your pom file from maven and away you go. Like most it can poll the svn repo for changes and make snapshots as we commit. Let me know what you guys think Nathan
