Hi

I would like to throw in my thoughts for what its worth. I am a fan of what the maven folks are trying to achieve. However, its greatest promise is also its biggest liability, and obstacle to adoption - the REPOSITORY! If you're working on a simple java application with no web components and no database access it's GREAT! It simplifies project set up, takes a lot of the labour out of the build and offers automation, reporting and other goodies. But if your trying to do a Web project with java technologies, e.g. el-api.jar, many other components (e.g. Icefaces) your in trouble!!!

Perhaps if there was a major vendor pushing the tool and the concepts (Sun perhaps?) then there may be a wider adoption. That would be great.

I'm not proposing that maven2 is the only (or the best) option, but if the major hurdles to its use in anything other than a trivial application were overcome, (the repository again) it could end up as the best game in town.

Thanks to the guys at Interface 21 for finally getting the SpringFramework included in the maven2 repository.

Hi

The role I'm currently in, we have adopted a very nice tool stack. A lot of up-front set up but after that its pretty much plain sailing. We have:
Eclipse 3.2.2 with
Checkstyle, PMD, Mylar, Subversion (Subclipse), JUnit plug-ins
Subversion version control (obviously)
maven2
Jira issue tracking
Confluence wiki
Cobertura test coverage
QuickBuild Continuous Integration system
and
Enterprise Architect for requirements and design in UML, and document generation.

With a lot of integration between the tools. It might seem a bit "heavyweight", but we need to satisfy very large (tax payer funded) customer and provide CMMI capabilities.