I got my words mixed up; I meant "and its dependencies" when I said "and its
dependent jar files".
Rusty Wright wrote:
If he's only using the documentation on the Apache Maven site I can
sympathize with him feeling that it's too complicated. This past
Saturday I was trying to figure out how to use the assembly plugin to
make a zip file containing my executable jar file and its dependent jar
files and wasted hours flailing around. Luckily, just before I went to
bed the lightbulb went off over my head and I remembered the Sonatype
book and looked at it and saw that they had a big chapter on it, so
Sunday I worked through that and was a happy camper.
The other experience that I've had is that some people are simply
resistant to change. If your colleague is like that my suggestion would
be, if you can afford to, is to become The Maven Guy and offer to set up
his builds for him; in other words, write his pom.xml files. Do it in
parallel with whatever he's using now and then demonstrate to him and
the rest of your colleagues how much better it is. Like the old saying
goes, you'll draw more flies with honey than you will with vinegar.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
