[EMAIL PROTECTED] wrote:
My approach on this was to sidestep the entire development team and go above them to the management team and sold them on the reporting capabilities instead of how simple the build becomes. I took an existing ant build based project and created a copy of it that was built with Maven. Once I had the basic mavenized build, I added Cobertura, Checkstyle, PMD, FindBugs, SureFire, TagList, JDepend, XRef and Dashboard reports and added a simple site.xml and a couple of simple APT based pages. Once I had that all working exactly the way I wanted, I showed each of the development managers (one at a time) the Dashboard report and showed them how they could drill down into the individual reports and see highlighted source code that showed where the code was not being tested or was violating one or more of the coding standards/guidelines. They were sufficiently impressed that things started to move forward. Once I had the managers on board, I knew it was a done deal... but I also knew I had to sell it to the naysayers in development. I showed them exactly the same dashboard report and showed them the POM and how easy it was to set up the reporting. Once they saw this, it was a pretty easy sell.
Another blow-them-away plugin is the release plugin.Set up a proper mavenised project as above, and make sure that the release process properly tags your code, uploads your artifacts, and uploads your documentation.
Arrange a demo where you run the command "mvn release:prepare release:perform", sit back, and show them what has been achieved. Show them the tag in source control, show them the artifact in the repository, show them the documentation.
The release plugin sells maven, IMHO. Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
