Hi.
In my custom plugin I’m using “maven-publish” plugin with number of publications (labels is list of custom objects):
project.publishing {
publications {
labels.each { info ->
"model${info.name}"(MavenPublication) {
artifactId "${info.artifactId}"
artifact project.tasks."${info.lower}Jar"
artifact project.tasks."source${info.name}Jar"
}
}
}
repositories {
maven { name 'release'; url extension.releaseRepository }
maven { name 'snapshot'; url extension.snapshotRepository }
}
}
Then I create task:
def releaseTask = project.task('modelRelease')
releaseTask.dependsOn project.tasks.matching { it.name.endsWith('ToReleaseRepository') }
releaseTask.dependsOn project.tasks.createTag
releaseTask.group = 'Model release'
releaseTask.description = 'Release new model'
When running ‘modelRelease’ task of my project:
Using gradle 2.3 everything works fine, all model artifacts upload to release maven repository successfully.
Using gradle 2.4 ‘modelRelease’ task ignores publish tasks:
$ ./gradlew model:tasks --all
...
modelRelease - Release new model [publishModelBasePublicationToReleaseRepository, publishModelDemoPublicationToReleaseRepository]
createTag
increaseMajorVersion
increaseMinorVersion
....
$ ./gradlew model:modelRelease
Parallel execution with configuration on demand is an incubating feature.
:model:increaseMinorVersion
:model:createTag
:model:increaseMajorVersion
:model:modelRelease
How can I fix it?