Skip to content

Conversation

@arey
Copy link
Contributor

@arey arey commented Jan 21, 2022

With Spring Framework 6.0.0-M2, the caches property is not valid and may be replaced by cacheNames

With Spring Framework 6.0.0-M2, the `caches` property is not valid and may be replaced by `cacheNames`
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jan 21, 2022
@snicoll
Copy link
Member

snicoll commented Jan 22, 2022

Thanks for the PR.

With Spring Framework 6.0.0-M2, the caches property is not valid

As far as I can see, it never was.

@snicoll snicoll added type: documentation A documentation task and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jan 22, 2022
@snicoll snicoll added this to the 5.3.16 milestone Jan 22, 2022
@snicoll snicoll self-assigned this Jan 22, 2022
@snicoll snicoll closed this in 5ef023a Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: documentation A documentation task

3 participants