Test against Gradle 5.3 #16294
Closed
Test against Gradle 5.3 #16294
Conversation
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
spring-projects-issues
added
the
status: waiting-for-triage
wilkinsona
added
type: task
|
Tested against example provided in gh-16211 which resulted in |
|
@pkostrzewa Thanks, but there’s no need to spend time on manual testing. This PR means that the test suite (that found the regression I reported to Gradle) will run against 5.3 automatically. The PR’s checks have passed and one of those checks is a CI build. |
snicoll
added a commit
that referenced
this pull request
Mar 25, 2019
* pr/16294: Test against Gradle 5.3
|
Thanks Christoph, this is now merged in |
|
@wilkinsona Thanks for information, actually it took no more than few minutes. But I wasn't aware of that fact. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Hi,
as Gradle 5.3 was released a few days ago, we should probably test against it.
Cheers,
Christoph