fix: Add Sonar 7 compatibility #125
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
|
Thanks a lot ! |
|
The release notes for 0.3.6 that includes this fix have been updated, but the Releases listing does not show the binary package for this release yet. Any idea when the official build package will be available? |
|
Bumping this issue. Is the release 0.3.6 ready yet? Or should I compile it manually for now? 😢 |
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.
Quick-fix for Sonar 7.0 compatibility
org.sonar.api.measures.PersistenceMode(deprecated since Sonar 5.6).org.sonar.api.web.CodeColorizerFormat(deprecated since Sonar 4.5.2, should useorg.sonar.api.source.Highlightableinstead)This fix seems to work, but more work should be done to ensure a full compatibility and to restore the features lost due to the deletion of
org.sonar.plugins.swift.colorizer.SwiftCodeColorizerFormat.Closes #118