On Nov 28, 10:43 pm, John Armstrong <[email protected]> wrote: > > Since starting with GWT (coming from Wicket which assumes Maven) I > have to say, I deeply miss Maven dependency management. My attempts to > mavenize my GWT Designer projects have failed and I lack the time to > debug and get things set-up right now (darn deadlines). > > The uniformity of build env is nice also but you get a lot of similar > functionality with the GWT tools as you point out. > > If you find yourself managing a lot of dependencies, manually > including jar files in support of other objectives or having to switch > between versions of libraries (usually internal libs for us) then I > think you'd get great benefit out of Maven. If all your looking for is > a compile tool in a fairly linear development environment (minimal > branching etc) then GWT has you covered.
I've been using Ivy (http://ant.apache.org/ivy/), a dependency management tool for Ant, and have been quite happy with it. It fits in quite well with GWT builds, and understands Maven-ized dependencies (knows how to read the dependencies from pom.xml files). Best of both worlds, IMO. I'm using it to do a good-sized multi-module build with Spring, Hibernate and GWT. -- 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.
