📦 davidmotson / GradleVersionBugReport

★ 0 stars ⑂ 0 forks 👁 0 watching
GradleVersionBugReport
📥 Clone https://github.com/davidmotson/GradleVersionBugReport.git
HTTPS git clone https://github.com/davidmotson/GradleVersionBugReport.git
SSH git clone git@github.com:davidmotson/GradleVersionBugReport.git
CLI gh repo clone davidmotson/GradleVersionBugReport
ZIP Desktop VS Code
David Motsonashvili David Motsonashvili Merge branch 'main' of github.com:davidmotson/GradleVersionBugReport 50ec8cc 5 years ago 📝 History
📂 main View all commits →
📁 app
📁 gradle
📄 build.gradle
📄 gradle.properties
📄 gradlew
📄 gradlew.bat
📄 README.md
📄 settings.gradle
📄 README.md

Expected Behavior

I expect that a version specified as [1.2.3] is different from 1.2.3

Current Behavior

When examining the DependencyResult object object for a resolved strict dependency, there doesn't appear to be any difference between strict and non-strict versions

Context

I maintain a gradle plugin which monitors strict versions and ensures that they are respected. This bug currently breaks the plugin, since there is no discernible difference between strict and non-strict versions.

Steps to Reproduce

  • Import this project
  • Run a build or sync
  • Observe generated error messages:
Observed in 6.3 and lower: com.google.firebase:firebase-messaging-directboot:20.3.0 -> com.google.firebase:firebase-messaging:[20.3.0] This correctly captures the strict dependency firebase-messaging-directboot has on firebase-messaging.

Observed in 6.4.1 and higher: com.google.firebase:firebase-messaging-directboot:20.3.0 -> com.google.firebase:firebase-messaging:20.3.0 This incorrectly erases the strict dependency.

Your Environment

Bug is reproducible with gradle version 6.4.1 and higher, change gradle version in wrapper to 6.3 to see expected behavior.