jdaugherty opened a new pull request, #43: URL: https://github.com/apache/grails-gradle-publish/pull/43
The pom's withXml closure and the module metadata doLast closure captured the project and the grailsPublish extension, so the pom and module metadata tasks could not be stored in the configuration cache, and both resolved configurations through the project when they ran. They are now actions that only hold values and providers: whether the project is a platform is decided when it is configured, and the resolved versions come from a provider, which the configuration cache evaluates when it stores the entry. Nothing is resolved while transitiveDependencies is disabled, and the versions are read from the resolution result of each configuration. The close and release tasks of the Nexus publish plugin cannot be stored when they run without its publishing tasks, as when a separate build closes the staging repository, so they are marked as not compatible with the configuration cache: such builds now run without storing an entry instead of failing. Every functional test build now runs with the configuration cache and fails on any problem, including the containerized release. A new test publishes twice, reusing the stored entry, and checks the platform managed versions in the pom and the module metadata. The bom example reads the Groovy version before its pom customization runs, the managed-dependency-versions example is published without the configuration cache since the Spring dependency management plugin does not support it, and the publications sharing artifacts are published one after the other, as tasks now run in parallel. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
