I figured out a way for this: Its working for me now. task myZip(type: Zip) { from ‘Reports/’ include ‘*’ include ‘*/*’ //to include contents of a folder present inside Reports directory archiveName ‘Reports.zip’ destinationDir(file(‘/dir1/dir2/dir3/’)) }
You can configure the snapshot and the release repository in the ‘Upload’ task (e.g. the uploadArchives) task: uploadArchives { repositories { mavenDeployer { repository(url: ‘http://myCompanyRepo.com:8081/releases’) { authentication(userName: ‘admin’, password: ‘password’); } snapshotRepository(url: ‘http://myCompanyRepo.com:8081/snapshots’) { authentication(userName: ‘admin’, password: ‘password’); } } } } For *-SNAPSHOT versions the snapshotRepository is used. Otherwise the releases repo is used.
[Edit april 2019] As Pedro has found, three months after I asked this question Gradle actually created a user guide for the Kotlin DSL which can be visited at https://docs.gradle.org/current/userguide/kotlin_dsl.html They also added a migration guide from Groovy to Kotlin at https://guides.gradle.org/migrating-build-logic-from-groovy-to-kotlin/ Answer: The syntax you ask for is tasks.test { // Use the built-in … Read more
The WAR task is aware of the artifacts it generates. task deployToTomcat(type: Copy) { from war.archivePath into “${tomcatHome}/webapps” }
Based on https://github.com/gradle/gradle/issues/6172#issuecomment-409883128 Amended in 2020 to take lazy task configuration and Gradle 5 into account. See answer’s history for older versions. plugins { id “java” } def test = tasks.named(“test”) { useJUnitPlatform { excludeTags “integration” } } def integrationTest = tasks.register(“integrationTest2”, Test) { useJUnitPlatform { includeTags “integration” } shouldRunAfter test } tasks.named(“check”) { dependsOn … Read more
It is very important to understand the distinction between task configuration and task execution: task eclipsify { // Code that goes here is *configuring* the task, and will // get evaluated on *every* build invocation, no matter // which tasks Gradle eventually decides to execute. // Don’t do anything time-consuming here. doLast { // `doLast` … Read more
Applying a plugin by plugin id is not supported in script plugins. You must use the plugin’s fully qualified class name. apply plugin: org.springframework.boot.gradle.plugin.SpringBootPlugin See this thread for more information. UPDATE: Updating plugin class name.
TL;DR – Use ignoreExitValue = true When I read the documentation for about the fiftieth time, I finally saw that there is a property, ignoreExitValue, which defaults to false. But if you set it to true, you can then perform your own tasks in the doLast block. task myTask(type:Exec) { workingDir ‘.’ commandLine ‘./myscript.sh’ ignoreExitValue … Read more
There is no such configuration out of the box for the java plugin. However you can build it yourself as follows: configurations { providedCompile } dependencies { providedCompile “javax.servlet:javax.servlet-api:3.+” } sourceSets.main.compileClasspath += configurations.providedCompile sourceSets.test.compileClasspath += configurations.providedCompile sourceSets.test.runtimeClasspath += configurations.providedCompile This adds the configuration, and puts all the dependencies in there on the compile classpaths of … Read more
The clean task is introduced by the base plugin. So you need to apply this plugin to get the clean task and the clean task rules for cleaning up specific task outputs: apply plugin:’base’