vlsi / vlsi-release-plugins

A set of plugins to simplify Gradle release tasks
Apache License 2.0
41 stars 13 forks source link

Gradle 8.1.1: Querying the mapped value of flatmap(provider(task 'distTar', class org.gradle.api.tasks.bundling.Tar)) before task ':release:distTar' has completed is not supported #70

Closed F21 closed 1 year ago

F21 commented 1 year ago

I tried to build a dry-run release of Avatica, which was recently updated to use Gradle 8.1.1.

The build fails with the following:

./gradlew prepareVote -PasfTestSvnUsername=test -PasfTestSvnPassword=test -PasfTestNexusUsername=test -PasfTestNexusPassword=test -PasfTestGitSourceUsername=test -PasfTestGitSourcePassword=test -Prc=0 --info
Initialized native services in: /root/.gradle/native
Initialized jansi services in: /root/.gradle/native
Received JVM installation metadata from '/opt/java/openjdk': {JAVA_HOME=/opt/java/openjdk, JAVA_VERSION=19.0.2, JAVA_VENDOR=Eclipse Adoptium, RUNTIME_NAME=OpenJDK Runtime Environment, RUNTIME_VERSION=19.0.2+7, VM_NAME=OpenJDK 64-Bit Server VM, VM_VERSION=19.0.2+7, VM_VENDOR=Eclipse Adoptium, OS_ARCH=amd64}
The client will now receive all logging from the daemon (pid: 64). The daemon log file: /root/.gradle/daemon/8.1.1/daemon-64.out.log
Starting 2nd build in daemon [uptime: 1 mins 43.544 secs, performance: 100%, GC rate: 0.00/s, heap usage: 0% of 512 MiB, non-heap usage: 43% of 384 MiB]
Using 20 worker leases.
Not watching /source since the file system is not supported
Watching the file system is configured to be enabled if available
File system watching is active
Starting Build
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Settings evaluated using settings file '/source/settings.gradle.kts'.
Projects loaded. Root project using build file '/source/build.gradle.kts'.
Included projects: [root project 'calcite-avatica', project ':bom', project ':core', project ':docker', project ':metrics', project ':metrics-dropwizardmetrics', project ':noop-driver', project ':release', project ':server', project ':shaded', project ':standalone-server', project ':tck', project ':shaded:avatica']

> Configure project :
Evaluating root project 'calcite-avatica' using build file '/source/build.gradle.kts'.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration3 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration3 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration3 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration3 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration4 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration4 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration4 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration4 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration5 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration5 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration5 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration5 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration6 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration6 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration6 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration6 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration7 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration7 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration7 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration7 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration8 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration8 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration8 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration8 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration9 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration9 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration9 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration9 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration10 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration10 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration10 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration10 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration11 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration11 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration11 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration11 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration12 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration12 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration12 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration12 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for root project 'calcite-avatica' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for root project 'calcite-avatica' as it is up-to-date.
Building Apache Calcite Avatica 1.24.0

> Configure project :bom
Evaluating project ':bom' using build file '/source/bom/build.gradle.kts'.
The configuration :bom:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :bom:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :bom:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :bom:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':bom' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':bom' as it is up-to-date.

> Configure project :metrics
Evaluating project ':metrics' using build file '/source/metrics/build.gradle.kts'.
The configuration :metrics:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':metrics' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':metrics' as it is up-to-date.

> Configure project :core
Evaluating project ':core' using build file '/source/core/build.gradle.kts'.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :core:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :core:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :core:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :core:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The com.google.protobuf plugin was already applied to the project: :core and will not be applied again after plugin: java-library
Caching disabled for Kotlin DSL accessors for project ':core' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':core' as it is up-to-date.
------------------------------------------------------------------------
Detecting the operating system and CPU architecture
------------------------------------------------------------------------
os.detected.name=linux
os.detected.arch=x86_64
os.detected.version=5.15
os.detected.version.major=5
os.detected.version.minor=15
os.detected.release=ubuntu
os.detected.release.version=22.04
os.detected.release.like.ubuntu=true
os.detected.release.like.debian=true
os.detected.classifier=linux-x86_64

> Configure project :docker
Evaluating project ':docker' using build file '/source/docker/build.gradle'.

> Configure project :metrics-dropwizardmetrics
Evaluating project ':metrics-dropwizardmetrics' using build file '/source/metrics-dropwizardmetrics/build.gradle.kts'.
The configuration :metrics-dropwizardmetrics:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics-dropwizardmetrics:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics-dropwizardmetrics:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics-dropwizardmetrics:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':metrics-dropwizardmetrics' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':metrics-dropwizardmetrics' as it is up-to-date.

> Configure project :noop-driver
Evaluating project ':noop-driver' using build file '/source/noop-driver/build.gradle.kts'.
The configuration :noop-driver:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :noop-driver:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :noop-driver:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :noop-driver:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.

> Configure project :release
Evaluating project ':release' using build file '/source/release/build.gradle.kts'.
The configuration :release:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :release:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :release:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :release:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':release' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':release' as it is up-to-date.

> Configure project :server
Evaluating project ':server' using build file '/source/server/build.gradle.kts'.
The configuration :server:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :server:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :server:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :server:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':server' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':server' as it is up-to-date.

> Configure project :shaded
Evaluating project ':shaded' using build file '/source/shaded/build.gradle'.

> Configure project :standalone-server
Evaluating project ':standalone-server' using build file '/source/standalone-server/build.gradle.kts'.
The configuration :standalone-server:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :standalone-server:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :standalone-server:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :standalone-server:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':standalone-server' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':standalone-server' as it is up-to-date.

> Configure project :tck
Evaluating project ':tck' using build file '/source/tck/build.gradle.kts'.
The configuration :tck:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :tck:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :tck:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :tck:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':tck' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':tck' as it is up-to-date.

> Configure project :shaded:avatica
Evaluating project ':shaded:avatica' using build file '/source/shaded/core/build.gradle.kts'.
The configuration :shaded:avatica:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :shaded:avatica:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :shaded:avatica:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :shaded:avatica:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Caching disabled for Kotlin DSL accessors for project ':shaded:avatica' because:
  Build cache is disabled
Skipping Kotlin DSL accessors for project ':shaded:avatica' as it is up-to-date.
All projects evaluated.
Task name matched 'prepareVote'
Selected primary task 'prepareVote' from project :
The configuration :signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :release:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :release:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :core:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :core:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :core:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :bom:apiElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :bom:enforcedApiElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :bom:enforcedRuntimeElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :bom:runtimeElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics-dropwizardmetrics:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :metrics-dropwizardmetrics:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :metrics-dropwizardmetrics:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :noop-driver:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :noop-driver:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :noop-driver:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :server:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :server:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :server:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :standalone-server:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :standalone-server:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :standalone-server:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :tck:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :tck:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :tck:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :shaded:avatica:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :shaded:avatica:signatures is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :shaded:avatica:signatures is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Closing Git repo: /source/.git

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':stageSvnDist'.
> Could not resolve all task dependencies for configuration ':releaseSignatures'.
   > Could not download distTarSha512.sha512 (project :release)
      > Querying the mapped value of flatmap(provider(task 'distTar', class org.gradle.api.tasks.bundling.Tar)) before task ':release:distTar' has completed is not supported

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 695ms
Some of the file system contents retained in the virtual file system are on file systems that Gradle doesn't support watching. The relevant state was discarded to ensure changes to these locations are properly detected. You can override this by explicitly enabling file system watching.
F21 commented 1 year ago

Sorry for the noise, looks like avatica was using 1.84, updating to 1.90 resoles this.