In my experience, Maven is pretty easy to understand and to deal with when you start a project from day 0 using it. When you try to migrate a project with its own build structure, with "crazy-or-not" build steps, then you will struggle A LOT with Maven to get the things done.
The XML aspect of Maven is not a problem when your build is stable enough. If you need/want to change your build frequently, I'd say you probably have serious problems with your project, or you really have a very special case that Maven wouldn't help anyway.
In summary: if you follow the Maven way™, you have no reasons to migrate away from it. But if you want custom build steps or project structure, and/or if you mix more stuff on your build steps (like deploy steps), similar to what is common to ANT builds, then Maven is not the best tool for you.
-- The XML aspect of Maven is not a problem when your build is stable enough. If you need/want to change your build frequently, I'd say you probably have serious problems with your project, or you really have a very special case that Maven wouldn't help anyway.
In summary: if you follow the Maven way™, you have no reasons to migrate away from it. But if you want custom build steps or project structure, and/or if you mix more stuff on your build steps (like deploy steps), similar to what is common to ANT builds, then Maven is not the best tool for you.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment