Property Changes Resulting from Sonar 10.4 Updates #151
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
* Property style changes from SonarQube 10.4 * Update PerlLanguageTest.java to reflect change in FILE_SUFFIXES_KEY property location. * Update PerlSquidSensorTest.java to reflect change in LogTester class originating from v9.15 change in sonar-plugin-api * Update build.gradle to reference 9.15 test-fixtures artifact * Update PerlLanguageTest.java to reflect change in defaults * Update PerlLanguageTest.java * Update PerlLanguageTest.java to create lists in JAVA! * Update PerlLanguageTest.java due to the downfalls of using a browser-based code editor... * Update PerlLanguageTest.java mapsettings.setproperty does not support list/array. * Typos everywhere... * IntegrationTests version updates and artifactory_url override to mavenCentral * Updates to tests and associated logic to reflect changes from v10.4 changes * Update ci.yml to set the repo based off the GITHUB_REPOSITORY variable vice hardcoded * Changes from sonar findings and env variable added to core build.gradle to run outside of parent project * Retriggering PR build * Update ci.yml to set env variable * Update ci.yml misread page * Update ci.yml stupid typo... * Update ci.yml more fun. * Update ci.yml adding branch name ref * Update build.gradle adding branch name ref for sonarscan * Update ci.yml updating action version and adding gradle setup * Correcting sonar branch name property reference * Update build.gradle testing to see if /ref issue is due to mapping * Update build.gradle * Remediate Sonar findings
Contributor
Author
|
@otrosien please review when you get a chance. |
Member
|
Thanks for the ping, I only saw your PR just now. |
Member
|
👍 |
|
Thanks for the work razac. |
Member
|
The CI pipeline is broken, but I'm trying to get it fixed right now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
SonarQube version changed the manner in which properties were handled resulting in issue reported in #150.
Updates include: