Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support constraints without version in GMM [Backport 6.9.x] #20189

Closed
ljacomet opened this issue Mar 16, 2022 · 1 comment · Fixed by #22359
Closed

Support constraints without version in GMM [Backport 6.9.x] #20189

ljacomet opened this issue Mar 16, 2022 · 1 comment · Fixed by #22359
Assignees
@ljacomet
Labels
a:bug in:gradle-module-metadata
Milestone
6.9.3

Comments

@ljacomet
Copy link
Member

See #20182 for details and #20188 for fix
@ljacomet ljacomet added this to the 6.9.3 milestone Mar 16, 2022
@hegyibalint hegyibalint mentioned this issue May 16, 2022
Closed
@ljacomet ljacomet self-assigned this Oct 11, 2022
ljacomet added a commit that referenced this issue Oct 11, 2022
@ljacomet
Add support for dependency constraint without version
0706242 
Prior to this change, a published Gradle Module Metadata that contained
a constraint without a version definition would result in a null
VersionConstraint instead of an empty one.
This caused issue during metadata serialization and potentially
resolution.
The field is not nullable and an empty version constraint is now used as
the default value.

Fixes #20189
@ljacomet ljacomet mentioned this issue Oct 11, 2022
Merged
@ljacomet ljacomet linked a pull request Oct 11, 2022 that will close this issue
Backports to 6x #22359
Merged
ljacomet added a commit that referenced this issue Oct 13, 2022
@ljacomet
Add support for dependency constraint without version
b95575c 
Prior to this change, a published Gradle Module Metadata that contained
a constraint without a version definition would result in a null
VersionConstraint instead of an empty one.
This caused issue during metadata serialization and potentially
resolution.
The field is not nullable and an empty version constraint is now used as
the default value.

Fixes #20189
bot-gradle added a commit that referenced this issue Oct 13, 2022
@bot-gradle @ljacomet
Merge pull request #22359 Backports to 6x
c18e0b2 
* Fixes #19523
* Fixes #20189

Co-authored-by: Louis Jacomet <louis@gradle.com>
@ljacomet
Copy link
Member Author

PR is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ljacomet ljacomet

Labels
a:bug in:gradle-module-metadata
Projects
None yet
Milestone
6.9.3
Development

Successfully merging a pull request may close this issue.

Backports to 6x gradle/gradle
1 participant
@ljacomet