Read source encoding from the standard sonar.sourceEncoding property#116
Open
Bazooper-blip wants to merge 1 commit into
Open
Conversation
- Changed the property key from `sonar.encoding` to `sonar.sourceEncoding` to align with updated configuration standards.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes the charset configuration key in
AnalysisOrchestrator: the code readsonar.encodingfromsonar-project.properties, but the standard Sonar property issonar.sourceEncoding— so a configured source encoding was silently ignored during analysis.This is the isolated bug-fix commit from #101, cherry-picked with @andrevfarias's authorship preserved, so the fix isn't blocked on the (much larger) legacy-IDE discussion in that PR.
Testing: full server Maven suite passes (127 tests, 0 failures).