Generate Release 0.2.3 to include StringUtils fix
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I've noticed https://github.com/Merck/sonar-r-plugin/commit/bfffd7bec344e756c7231ace9eda4d151c7bace2 appears to include a fix for issue I've hit when using latest 0.2.2 Release when trying to run from Azure DevOps.
##[error]ERROR: Error during SonarScanner execution
##[debug]Processed: ##vso[task.logissue type=error;]ERROR: Error during SonarScanner execution
ERROR: Error during SonarScanner execution
##[error]java.lang.NoClassDefFoundError: org/sonar/api/internal/apachecommons/lang/StringUtils
##[debug]Processed: ##vso[task.logissue type=error;]java.lang.NoClassDefFoundError: org/sonar/api/internal/apachecommons/lang/StringUtils
java.lang.NoClassDefFoundError: org/sonar/api/internal/apachecommons/lang/StringUtils
##[error]at com.msd.gin.common.sonar.LintRSensor.readLintrOutputFile(LintRSensor.java:88)
##[debug]Processed: ##vso[task.logissue type=error;]at com.msd.gin.common.sonar.LintRSensor.readLintrOutputFile(LintRSensor.java:88)
at com.msd.gin.common.sonar.LintRSensor.readLintrOutputFile(LintRSensor.java:88)
##[error]at com.msd.gin.common.sonar.LintRSensor.execute(LintRSensor.java:67)
Appears there is no release that includes above fix yet.
I built out latest of master locally and this has resolved my issue, so may benefit others if a new release is created.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect commit bfffd7bec344e756c7231ace9eda4d151c7bace2 and the current master branch to confirm that the StringUtils fix is included. Follow the repository's release process to generate and publish version 0.2.3, then verify that the released artifact contains the fix for the reported Azure DevOps failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100