Configuration metadata for logging.charset.* has invalid reference for java.nio.charset.Charset #24851
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: bug
|
Thanks, @dreis2211. I've opened #24852 to see if we can catch this sort of mistake automatically. |
snicoll
changed the title
snicoll
pushed a commit
that referenced
this pull request
Jan 17, 2021
This was referenced Mar 11, 2021
Closed
Merged
Merged
Closed
Bump spring-boot-starter-parent from 2.4.2 to 2.4.3
checkmarx-ltd/checkmarx-spring-boot-java-sdk#106
Closed
This was referenced Mar 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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,
this PR fixes the configuration metadata for
logging.charset.consoleandlogging.charset.fileby adjusting the wrong type information.I only noticed in IDEA that no warning was shown when I entered a wrong charset encoding.
I guess other places consuming the metadata could be affected as well.
Cheers,
Christoph