On Fri, 25 May 2018 15:58:34 +0100 Neil C Smith <[email protected]> wrote:
> On Fri, 25 May 2018 at 02:02 Tim Boudreau <[email protected]> wrote: > > > IMO, Gradle is a step backward for build systems - scriptability > > leads to fragile systems, and ones that are impossible for tools to > > reason about. > > > > https://timboudreau.com/blog/maven/read > > > > > Nice article! I know you link it in a comment, but also worth posting > Jaroslav's page on this too - http://wiki.apidesign.org/wiki/Gradle Interesting article. I personally would favor Groovy code I can see and read vs some Maven plugin. Or worse having to make a maven plugin vs just coding in Groovy. That seems like more work. Making a plugin just to use it in XML vs direct Groovy in the build file. Groovy is an Apache project and a programming language unlike XML. Are we not programmers? Or we rather write XML vs code? I believe Gradle also has better Ant integration than Maven. Neither article talks about that aspect at all... Which could be used for any Netbeans transition, maybe. Not sure about NB ant modifications. https://docs.gradle.org/current/userguide/ant.html Retired https://maven.apache.org/ant-tasks/index.html Active https://maven.apache.org/plugins/maven-antrun-plugin/ Usage looks like a total pain... https://maven.apache.org/plugins/maven-antrun-plugin/usage.html Maven Ant integration seems inferior to Gradle Ant integration. I could be wrong there. Odd given that both Ant and Maven are Apache.... -- William L. Thomson Jr.
pgp_xrwmovO7F.pgp
Description: OpenPGP digital signature
