Remove invocation of Bean methods. #2867
Merged
Conversation
This file contains 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
|
good. thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not allowed to invoke Bean methods when turning off proxying (being allowed to invoke them in the first place has always been a terrible feature of Spring anyways...).
I didn't take a detailed look at whether this fixes the failure in #2864 but not surprised if it does. Instead of examining and debugging failures, I just went through every reference in
@InternalZipkinConfigurationand ctrl-clicked on@Beanmethods to see if they have references.Also overrides the pretty printer for Jackson so the output always uses
\nso tests pass on Windows.