Add tests for buildscript map notation with GString version variables#6780
Closed
Jenson3210 wants to merge 1 commit intomainfrom
Closed
Add tests for buildscript map notation with GString version variables#6780Jenson3210 wants to merge 1 commit intomainfrom
Jenson3210 wants to merge 1 commit intomainfrom
Conversation
…spath deps
Covers UpgradeDependencyVersion handling of the legacy buildscript pattern where
dependency versions use map notation with GString variable references in ext blocks:
classpath group: '...', name: '...', version: "${springBootVersion}"
Includes tests for guava and spring-boot-gradle-plugin upgrades.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
UpgradeDependencyVersionhandling the legacy buildscript pattern with map notation and GString version variablesclasspath group: '...', name: '...', version: "${varName}"in buildscript dependencies blocksContext
These tests were written while investigating a customer report that the Spring Boot 4 migration recipe was not making changes on a build.gradle using the legacy
buildscript/apply pluginpattern with map notation dependencies. The investigation confirmed the recipe works correctly for this pattern.