I mistakenly ended up with the following in my build.gradle:
implementation "com.auth0:auth0:1..0"
Previously it was:
implementation "com.auth0:auth0:1.19.0"
What is the expected behaviour here? The docs don’t mention this pattern for version numbers: https://docs.gradle.org/current/userguide/single_versions.html
To my surprise this still compiled and continued to use 1.19.0, even when appending --refresh-dependencies
:
./gradlew dependencyInsight --configuration compileClasspath --dependency com.auth0:auth0 --refresh-dependencies
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.5.1/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing
> Task :dependencyInsight
com.auth0:auth0:1.19.0
variant "compile" [
org.gradle.status = release (not requested)
org.gradle.usage = java-api
org.gradle.libraryelements = jar (compatible with: classes)
org.gradle.category = library
Requested attributes not found in the selected variant:
org.gradle.dependency.bundling = external
org.gradle.jvm.version = 8
]
Selection reasons:
- By conflict resolution : between versions 1.19.0 and 1..0
com.auth0:auth0:1.19.0
\--- com.auth0:mvc-auth-commons:1.3.0
\--- compileClasspath
com.auth0:auth0:1..0 -> 1.19.0
\--- compileClasspath
A web-based, searchable dependency report is available by adding the --scan option.
BUILD SUCCESSFUL in 23s