-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle does not return dependencies at all #9255
Comments
wkl3nk
added
bug
Issues that are considered to be bugs
to triage
Issues that need triaging
labels
Oct 8, 2024
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 8, 2024
Starting with Gradle 8.2, a property that defines if a gradle configuration is deprecated now can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all gradle configurations are considered deprecated. As a result, no dependencies for no gradle configurations are returned. Fixes oss-review-toolkit#9255 Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
Still interesting how this can result in seeing less (or zero) dependencies. I would have assumed that if the Gradle analyzer does not exclude enough, we'd rather see too many dependencies. |
sschuberth
added
analyzer
About the analyzer tool
and removed
to triage
Issues that need triaging
labels
Oct 8, 2024
wkl3nk
changed the title
Gradle does return dependencies at all
Gradle does not return dependencies at all
Oct 8, 2024
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 8, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes oss-review-toolkit#9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 8, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes oss-review-toolkit#9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 8, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes oss-review-toolkit#9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 9, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes oss-review-toolkit#9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
wkl3nk
added a commit
to boschglobal/oss-review-toolkit
that referenced
this issue
Oct 9, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes oss-review-toolkit#9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
sschuberth
pushed a commit
that referenced
this issue
Oct 9, 2024
Starting with Gradle 8.2, a property that defines if a Gradle configuration is deprecated can be an empty list instead of just null. This is misinterpreted by the Gradle analyzer plugin, and all Gradle configurations are considered deprecated. As a result, no dependencies for Gradle configurations are returned. Fixes #9255. Signed-off-by: Wolfgang Klenk <wolfgang.klenk2@bosch.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I use the Analyzer CLI to directly analyze a checked-out repository.
I explicitly use the Gradle package manager, not GradleInspector.
The repository is a simple gradle-based project with a little bit of Spring Boot.
Expected behavior
I would have expected > 60 dependencies, but I get 0.
Analysis
The Gradle plugin iterates over the gradle configurations, tries to exclude (plugin) configurations that are deprecated.
Since Gradle 8.2, the configuration property
resolutionAlternatives
has changed to aImmutableList
, and this property can no longer benull
, but instead the list can be empty. The code inside of the Gradle plugin does not reflect that change.On the other hand, the code in the GradleInspector does reflect this change: 1d172c9
Please hang on for a PR.
The text was updated successfully, but these errors were encountered: