You just need to set the group property of your task. Eg (from http://mrhaki.blogspot.co.uk/2012/06/gradle-goodness-adding-tasks-to.html) task publish(type: Copy) { from “sources” into “output” } configure(publish) { group = ‘Publishing’ description = ‘Publish source code to output directory’ }
To solve this I had to first kill the Java(TM) Platform SE binary process and then I was able to delete the whole /Users/<username>/.gradle/caches folder which allowed Gradle commands to work once again. I believe this issue may have happened for me as a result of adding a new dependency to my build.gradle file through … Read more
For some reason, running gradle in daemon mode causes a null console object. If you specify the appropriate command line flag, ./gradlew assembleRelease –no-daemon it’ll work.
You can call ./gradlew –stop in a terminal and it will kill all Gradle processes.
Have you tried: configurations.each { println it.name } ?
You can declare common dependencies in a parent script: ext.libraries = [ // Groovy map literal spring_core: “org.springframework:spring-core:3.1”, junit: “junit:junit:4.10” ] From a child script, you can then use the dependency declarations like so: dependencies { compile libraries.spring_core testCompile libraries.junit } To share dependency declarations with advanced configuration options, you can use DependencyHandler.create: libraries = … Read more
The command is gradle dependencies, and its output is much improved in Gradle 1.2. (You can already try 1.2-rc-1 today.)
targetCompatibility and sourceCompatibility maps to -target release and -source release in javac. Source is basically the source language level and target is the level of the bytecode that is generated. More details can be found in the Cross-Compilation Options for javac section of Tools Reference for Java 8, for Java 11, for Java 17, or … Read more
On Mac, Linux and Windows i.e. on all 3 of the major platforms, Gradle stores dependencies at: ~/.gradle/caches/modules-2/files-2.1
It has to do with extensibility, reuse and avoiding duplication. For one built in tasks can be extended like: task CopyAndThen(type: Copy) { doFirst { println “this is before the actual copy” } doLast { println “this is after the actual copy” } } The second common scenario that comes to mind is with multi … Read more