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.
I hope that this helps you out. At 7:16 PM -0700 10/20/08, cvr wrote: >I have a colleague has recently become a very vocal opponent of Maven. The >problem is that we're behind a corporate firewall, and he has had a lot of >difficulty getting Maven to work (I googled "firewall" and created a >~/m2./settings.xml file appropriately). > >His arguments have been: > >- "The build system should be more complicated (harder to run, harder to >configure) than the software" >- "Why all this configuration for a glorified WGET?" >- "Why do you need a shared repository (~/.m2/repository)? Disk space is >really cheap" >- "What's wrong with just checking the jars in to source control under lib" >- "I just have a build script that I run to compile my project, what's so >hard about that?" (ed. note: it's a bash script) > >Having struggled with projects that had *no* build script (from the README: >"step 1: open up Eclipse and click compile"), projects with undocumented >dependencies (yay, ClassNotFoundException at runtime), and having fought >multi-module ant builds for two years - Maven has worked out wonderfully. >However, I can't seem to get this across. His mind is (angrily) closed. > >I'm just wondering if others on this forum have encountered similar >hostility and you coped with it. >-- >View this message in context: http://www.nabble.com/Advice-on-dealing-with-hostility-to-Maven-2-tp20082277p20082277.html >Sent from the Maven - Users mailing list archive at Nabble.com. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] Dale Chapman, Corporate Architect, Common Services Medavie 506-867-4430 [EMAIL PROTECTED] Debugging is at least twice as hard as programming. If your code is as clever as you can possibly make it, then by definition, you are not smart enough to debug it. - Brian Kernighan ----------------------------------------------------------------------- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l’entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous puissions effectuer la correction à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu de la transmission originale ainsi que toute réponse ultérieure. Merci. -----------------------------------------------------------------------
