Open Steppschuh opened 6 years ago
Just lost some hours because of this issue. I added configuration on demand together with some other Gradle changes and it was not clear at all that this was the cause as the problem is completely silent.
Wow, this is still not supported after 4 years?
When configureOnDemand=true
, If I run these commands one after the other, the group of the -domain
dependency is not resolved and it's wrong
./gradlew :ble:generatePomFileForAarPublication
./gradlew :ble-domain:generatePomFileForAarPublication
Snippet from generated pom for ble
module
<dependency>
<groupId>ProjectName.ble</groupId>
<artifactId>ble-domain</artifactId>
<version>0.3.0</version>
</dependency>
The group is resolved as expected if you run one after the oner
./gradlew :ble-domain:generatePomFileForAarPublication :ble:generatePomFileForAarPublication
And now, the group is correct
<dependency>
<groupId>my.company</groupId>
<artifactId>ble-domain</artifactId>
<version>0.3.0</version>
</dependency>
Come on JFrog, give some ❤️ to this plugin!
Expected behaviour
Executing
./gradlew artifactoryPublish
publishes artefacts. Output:Actual behaviour
Executing
./gradlew artifactoryPublish
doesn't publish any artefacts. Output:Steps to reproduce
org.gradle.configureondemand=true
to gradle.propertiesConfiguration on demand is an often (1, 2, 3) recommended build performance optimization for larger projects with multiple modules.
Finding the cause of this issue burned quite a few hours. There should be at least a warning or error message if the artifactory plugin can't work properly with that flag enabled.