On Sunday, December 12, 2010 3:58:17 PM UTC, koma 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 ? - Large existing repository : in my experience, more often than not, some transitive dependency is screwed and you're overwriting it in your pom; - consistent layout : isn't GWT suggesting a layout already ? - Setting up a project is really fast : isn't the GWT plugin doing that really nice for you ? 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 ? You're right - it is a pain and a struggle! In my case I put that down to me being quite new to a lot of the technologies. Often I've thought about just doing it the default GWT way. Then I think of the Spring jars required as I want to use spring-webmvc and spring-security. I also know that I'm going to want to update those dependencies as newer versions are released. I really don't want to have to think about where to get an AOP alliance jar and what version I need (for example). This post on StackOverflow is giving me good reason to pursue it: http://stackoverflow.com/questions/3589562/3589974#3589974 My position may change if I continue to have problems but I like the scalability of it. Pete -- 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.
