Gradle release-candidate is shown regardless of exclusion rules
See original GitHub issueI have Gradle wrapper version 5.4.1 defined and your plugin v0.21.0 applied in a project of mine. I also have the latest resolutionStrategy
snippet from your README.md applied in order to filter out release candidates of certain dependencies. When I execute the Gradle dependencyUpdates
task I however see the following:
Gradle release-candidate updates:
- Gradle: [5.4.1 -> 5.5-rc-1]
I would have expected that 5.5-rc-1
is hidden. Is this a special handling for Gradle dependencies or is this a configuration error for the exclude rules?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Gradle 7.6 Release Notes
Attribute disambiguation rules control the variant of a dependency selected by Gradle when: multiple variants of a dependency exist with different compatible ...
Read more >Release Candidate - Gradle
The current Gradle release candidate version is 7.6 RC4, released on 22 Nov 2022. The distribution zip file comes in two flavors: Binary-only ......
Read more >Gradle 4.6-rc-2 Release Notes
The Gradle team is pleased to announce Gradle 4.6. First and foremost, this release of Gradle includes built-in support for JUnit Platform and...
Read more >Learning the Basics - Gradle User Manual
String) causes the given candidate version to be explicitly rejected, in which case the candidate will not be considered for the selector.
Read more >Gradle 1.0-milestone-7 Release Notes
So far, forcing versions in Gradle required the user to add extra first level dependency and then configure it to be forced. This...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks! For completeness … and because I did realized the
-D
vs.-P
:… works fine.
dependenyUpdates.gradleReleaseChannel = “current” Or -DgradleReleaseChannel=current
https://github.com/ben-manes/gradle-versions-plugin/blob/4f0b7ce7b8c76531fcd0808c46a00b0a9b582d65/src/main/groovy/com/github/benmanes/gradle/versions/updates/DependencyUpdatesTask.groovy#L89
On Thu, Jun 6, 2019 at 2:54 AM Tobias Preuss notifications@github.com wrote: