Closed jeusdi closed 7 years ago
By default the base plugin already assigns a specific WAR file. You can reconfigure the task and assign a different "deployable".
remoteContainers.each { config ->
task "deployDev${config.name.capitalize()}"(type: com.bmuschko.gradle.cargo.tasks.remote.CargoDeployRemote) {
...
dependsOn = [createDevelopmentWar]
deployables = [new com.bmuschko.gradle.cargo.convention.Deployable(file: createDevelopmentWar.archivePath)]
}
}
The key to understanding what and how you can do it is to check the Javadocs for the task type. Please make sure to explore before opening an issue.
I'm getting this message when I perform my deploy task:
As you can see it's trying to pick the artifact from
build\libs
.Nevertheless,
:deployDevWildfly10
is a custom madeCargoDeployRemote
task type:As you can see it depends on
createDevelopmentWar
(a custom madeWar
task type):As you can see, I set
destinationDir
tofile("$buildDir/dist")
. So, the artifact is going to be generated inbuild\dist
instead of inbuild\libs
. Is there anyway to change this behaviour?It works if I delete
archiveName
anddestinationDir
parameters from custom made war task: