On Monday, September 29, 2014 2:30:38 AM UTC-5, fabrizio.giudici wrote: > > It depends. When you have heterogeneous groups where you have to enforce > some order, declarative is better because you can force people to stick > with a standard way to do things. >
Maven gives a very superficial illusion of forcing declarative builds. However, it is common to see imperative logic in Maven builds in the form of ant tasks or plugins. Some builds really do justify imperative script logic, Gradle just supports this with an actual programming language. If you have a standard build, declarative build definitions are great. Gradle and SBT really don't stop that. In fact, they make simple declarative builds much more concise than Maven's mountains of XML. Maven is designed with fixed build tasks and a fixed pre-defined lifecycle. Many projects have genuine need for custom build steps. Maven expects you to rig your custom build steps into the predefined steps. Gradle lets you define new tasks and task dependencies as you need them. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to javaposse+unsubscr...@googlegroups.com. To post to this group, send email to javaposse@googlegroups.com. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/d/optout.
