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]
