On Wed, May 9, 2007 12:30 pm, Siegfried Goeschl wrote: > +) a related problem is that many companies hire juniors for this > setting up and maintaining a build system - it is not real programming > after all ... :-) ... later on the know better
I've seen over an over again how a lack of basic software discipline can reduce a quickly running project down to an absolute crawl. One of the most key benefits of a system like maven is that it (within limitations) enforces discipline within a project. When you've made a policy decision that the maven release plugin (for example) will be used to make releases, you are now implicitely saying that the underlying code needs to build, the version control rules need to be followed properly, the maven repository to which you're publishing releases needs to be configured properly. Instead of trying to educate developers on some weird home grown way of maintaining software discipline (a task akin to herding cats), you say let's use the maven way - something you learn once, and apply everywhere. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
