On 12 December 2010 07:58, koma <[email protected]> wrote: > Really, tell me : what does Maven bring you expect for the above > problems ? > > - dependency management : Is is really easier ? what's so hard about > downloading a jar and setting the build path ? sure you're not > spending more time adjusting the pom ?
Ever tried to do maintenance on one of such horror projects? All JARs are available in one (or more!) lib directories. Most are called abc.jar so you have no clue of their versions. Of the few that actually have a version number (i.e. something like abc-1.3.jar) it turns out that it's not really version 1.3. [That's because the build was referring to them by name so when a new version was needed the developer simply overwrote the existing JAR with the new JAR without changing the name.] Unfortunately, I'm talking from personal experience, Ant builds are almost always horrific. It's a sad fact of life that most of the time builds are created by developers who don't know much about how to create a good build: "how hard can it be?". In general, Maven forces even newbies to do things the right way. > - Large existing repository : in my experience, more often than not, > some transitive dependency is screwed and you're overwriting it in > your pom; Sounds like FUD. I know it happens but it's not common. I've never run into it. > - consistent layout : isn't GWT suggesting a layout already ? Good point, why doesn't GWT follow established Maven conventions? Maven's directory structure existed long before GWT was even an idea in the original developer's mind. Why not reuse existing rules and conventions? We wouldn't have to fight GWT all the way to hammer GWT projects into a proper Maven structure. :-) And note that following Maven conventions doesn't mean you have to use Maven, you could still use Ant! > - Setting up a project is really fast : isn't the GWT plugin doing > that really nice for you ? No it isn't and it shouldn't. That's what I've got my IDE and Maven for. GWT should stick to doing what it's good at not try to do everything else as well. > browse this group and you'll notice so many folks struggling with > maven instead of struggling with code! > and didn't maven promise to get you coding in the first place ? Absolutely true. I ran into that too initially. But it's not Maven's fault, it's because GWT likes to do everything in unconventional ways. Hopefully, things will improve now that the GWT team is trying to support Maven better. I encourage you to read through the link PeteUK sent. (Please don't misunderstand, Maven is far from perfect and some of the core Maven developers display some real hubris on occasion. It is, however, by far the best we've got.) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
