The role of gradle -


this might stupid question. in company usage of gradle starting emerge. have been learning basic of gradle , use small projects.

because of gradle's flexibility, usage can vast. i'm coming maven , i'm confused role of gradle in our project general-purpose tool.

here of usages pops questions in head:

  • gradle tasks treated cli sub commands. command line arguments passed properties. seems me project can written normal java/groovy uses library common-cli or args4j quite mature (supporting help, usage, etc).
  • some of sub projects checked out using gradle instead of using svn:externals.

my question not how?, it's more should it?

gradle gives lot of flexibility, indeed. uses groovy - can create kind of workflows , commands. i'm not sure if best practice though.

the best when can leverage declarative side of gradle (via java plugin), same way maven - build conventions, , may have customizations if need build artifacts. gradle kind of tool merges benefits maven , ant, replacing xml groovy dsl.

what described sounds more project custom structure , thing leveraged task execution engine. same ant. didn't mention, instance, if you're using plugins.

some of sub projects checked out using gradle instead of using svn:externals

i think same other build tool out there. me sounds quite strange - there's cli tool (svn, git, hg, ). person established had desperate wish accommodate commands 1 tool, cases may quite useful, why not. didn't provide more context, sounds overuse of scripting , over-engineering.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -