Usually when I hear someone complain about 'maven is sooo complicated, why do we need it', it comes from people who do not know how to _really_ manage a project.
Most of them never did: .) nightly builds .) automated regression tests .) any kind of continous integration at all .) release management (sometimes they at least do manual tagging before shipping products to their customers) .) maintenance branches .) good documentation .) product planing .) source quality control etc So they sometimes really don't see all the points where their life is getting sooo much easier. Or from a philosophic point: most people only see what is getting worse but take improving situations as a matter of course. Regardless of how big the improvement is. LieGrue, strub --- David C. Hicks <[EMAIL PROTECTED]> schrieb am Di, 21.10.2008: > Von: David C. Hicks <[EMAIL PROTECTED]> > Betreff: Re: Advice on dealing with hostility to Maven 2 > An: "Maven Users List" <[email protected]> > Datum: Dienstag, 21. Oktober 2008, 4:38 > I've encountered some level of the frustration that > you're referring > to. I have found that it mostly stems from ignorance of > Maven more than > anything else. My normal reaction, though, is a very > simple one. I > offer to turn maintenance of the build system over to > whoever is > complaining. That usually shuts them up. > > The ones who complain the most are often those who somehow > missed out on > the fact that most development tools are actually > command-line > oriented. They just don't know how to behave if they > don't have a > button to click on. That's when I introduce them to > M2Eclipse or a > well-placed external tool. The fact still remains that if > given the > choice between maintaining a build themselves or dealing > with what I > give them, they succumb to my will. :-) > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
