cvr wrote:
His arguments have been:- "The build system should be more complicated (harder to run, harder toconfigure) 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.
I have encountered some shockingly broken build systems out there, but in all cases people recognised they were broken, and were grateful when it was fixed for them.
Unfortunately I suspect that your colleague lacks experience with building projects any larger than trivial, and the only solution is to work around them until they gain enough experience to "get it".
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
