Not using interactive tasks would be going against the very philosophy behind Gradle. "Unlike the build file formats of Ant and Maven, Gradle’s Groovy-based build files allow you to do general-purpose programming tasks in your build file. This relieves much of the frustration developers have faced in lacking control flow in Ant or being forced into plug-in development in Maven to accomplish nonstandard tasks."
Lower level build tasks may require little user interaction typically those tasks linked to building the system and it's components. Higher level tasks will definitely involve user-interaction which is where Groovy comes into the equation. In fact, it makes Gradle’s use of Ant simpler than directly using Ant, partly by leveraging Groovy’s AntBuilder functionality. I have used Ant builder before for tasks such as: 1. Creating a charts of accounts; 2. Building a catalogue; 3. Building a webstore; 4. Building a theme. These are some examples of build tasks that are on a higher level with less generic application. My 2 cents. Gavin On 10 Jul 2016 1:02 PM, "Jacques Le Roux" <[email protected]> wrote: > Le 10/07/2016 à 12:48, Jacques Le Roux a écrit : > >> Hi, >> >> See https://issues.apache.org/jira/browse/OFBIZ-7773 and >> https://issues.apache.org/jira/browse/OFBIZ-7772 >> >> Opinions (about the question in title: "Should we?") >> >> Thanks >> >> Jacques >> >> >> > This could help > https://mrhaki.blogspot.fr/2010/09/gradle-goodness-get-user-input-values.html > > Jacques > >
