> I can remember other > colleagues telling my "Damn, I spend the last day resolving a > maven problem...".
Before Maven, I would spend just as much, if not more time, fighting with builds. As for the link you provided, I think there is some truth to it. But in my view the pros far out way the cons. So ya sure Maven may need to download artifacts a lot. But because everything is modular, very rarely do you need to compile a lot of code. This greatly speeds up build times. So overall, we have seen our build times actually decrease when we went to Maven, not increase. And having a local repo manager does solve most of the issues discussed on that blog (in my view anyway). Contrary to what the author states. We have had some problems with build reproduciblity though. But it was because of downloading artifacts. I believe, although I have not confirmed, is that a plugin is behaving differently on Windows than it does on Linux. But I wouldn't say this is a core Maven issue and conclude that Maven is "broken by design". I would say the design is very sound. My 2 cents... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
