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.

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

refreshVersionsMigrate doesn't replace dependency notations that are using version ranges #447

Open
LouisCAD opened this issue Oct 1, 2021 · 0 comments
Labels
problem Something isn't working

Comments

@LouisCAD
Copy link
Member

LouisCAD commented Oct 1, 2021

Steps to reproduce

Migrate a project that has implementation 'junit:junit:4+' in one of its build.gradle files.

Result

The version is added as is into the versions.properties file, but the dependency notation isn't replaced, so it stays unused.

Having a version range in a version entry in the file works fine even when migrating the dependency notation to use the version placeholder, so the issue is only replacement in the build file.

@LouisCAD LouisCAD added the problem Something isn't working label Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant