I completely agree.
I'd go one step further with your building it on another machine and say that
it has to build on another machine that's a different platform. I.e., if
you're building on unix it must also build on Windows, or vice versa. And if
you're building it in eclipse with the maven plugin it must also build outside
of eclipse from the command line.
Graham Leggett wrote:
Rusty Wright wrote:
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.
In my experience, some people on projects believe that if it works for
them, then everything is fine. In practice, the build often works for
them, but doesn't work for anybody else, and they don't care.
What works in this kind of environment is a general rule that says this:
"Your work is not done until it can be shown to build and run cleanly on
a second machine other than your own".
Being the "maven guy" also works very well, especially if you are also
the continuous integration guy, and the CI server is the "second
machine" above.
In many cases resistance to change comes about simply because people are
too busy to stop and "sharpen the saw".
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
