Skip to content

DATACMNS-703 - PropertyReferenceExceptions now exposes potential matches. #125

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

Closed
wants to merge 1 commit into from

Conversation

odrotbohm
Copy link
Member

We now use Spring's PropertyMatches to build up the exception message and include a list of potentially meant properties.

Removed unused config file for tests along the way.

This waits for Spring 4.1.7 to be released.

…hes.

We now use Spring's PropertyMatches to build up the exception message and include a list of potentially meant properties.

Removed unused config file for tests along the way.
odrotbohm added a commit that referenced this pull request Jul 6, 2015
We now use Spring's PropertyMatches to build up the exception message and include a list of potentially meant properties.

Removed unused config file for tests along the way.

Original pull request: #125.
@odrotbohm odrotbohm self-assigned this Jul 8, 2015
@odrotbohm odrotbohm closed this Jul 8, 2015
Aloren pushed a commit to Aloren/spring-data-commons that referenced this pull request Jun 20, 2019
Anticipating a change in Spring Boot 1.4.1 to support child context
creation without (needless) re-initialization of the logging system,
we need to carefully manage the lifecycle, in particular calling
cleanUp() when we know there are changes in the pipeline.

Fixes spring-projectsgh-125
@mp911de mp911de deleted the issue/DATACMNS-703 branch November 6, 2020 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant