-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bug: Multiple versions in gradle.properties #10
Comments
I've opened a PR to fix this issue: #11 It was only updating the last version, when there was now new line after the last version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @patrikerdes,
I found another issue. When the version variables are set in the
gradle.properties
file only the last version is updated.Here is an example:
See https://github.com/usr42/use-latest-issues/tree/multiple-versions-in-gradle_properties
gradle.properties:
build.gradle:
When running
./gradlew useLatestVersions && ./gradlew useLatestVersionsCheck
the check is failing:The gradle.properties was updated to:
Only the last variable (here
hibernateValidatorVersion
) is updated.If I change the ordering of the variables in
gradle.properties
, thenjunitVersion
(now the last variable) is updated, but nothibernateValidatorVersion
.Thanks and cheers,
usr42/Balthasar
The text was updated successfully, but these errors were encountered: