copy configuration attributes from runtimeClasspath to developmentOnly and testAndDevelopmentOnly - #51493
Open
wakingrufus wants to merge 1 commit into
Open
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
…y and testAndDevelopmentOnly fixes spring-projectsgh-51492 include refactors in the modified code to better comply with Gradle lazy APIs Signed-off-by: John Burns <wakingrufus@gmail.com>
wakingrufus
force-pushed
the
fix-configuration-attributes
branch
from
August 28, 2026 20:39
820e2f8 to
6a432fc
Compare
wakingrufus
marked this pull request as ready for review
August 28, 2026 20:39
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
2 participants
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.
copy configuration attributes from runtimeClasspath to developmentOnly and testAndDevelopmentOnly
fixes gh-51492
the developmentOnly and testAndDevelopmentOnly do not specify attributes, which can lead to Gradle selecting the wrong variant, or failing to resolve due to an ambiguity error. This can be avoided by following best practices regarding configuration attributes in gradle:
https://docs.gradle.org/current/userguide/best_practices_dependencies.html#use_attributes_on_configurations
the productionRuntimeClasspath was previously fixed in b01235e so a similar fix is needed for these configurations as well
I also included refactors in the modified code to better comply with Gradle lazy APIs