maven - Change behavior in sonar.java.binaries property -
Disclaimer: I have tried posting this message on Sonar's user mailing list.
We are using SonarQube 4.5.1 and facing this context on some projects this day using Property sonar.java.binaries .
We updated the version of Java plugin yesterday 2.8 (we were using 2.5.1 earlier).
There is an error in the analysis:
[error] [20: 43: 58.997] invalid value for sonar.java.binaries [error] Any files or directories match No account '/PATH_TO_JENKINS_WORKSPACES/sonar/PROJECT_NAME/release/PROJECT_JAR.jar' In pom.xml, sonar.java.binaries is the property with the value: $ {Baseir} / release / $ {project.artifactId} .jar
Variable changes are good on analysis and the jar is present in the repository.
This is my test:
- On returning to version 2.5.1, sonar analysis is fine
- When using version 2.8, if
Sonar.java.binariesanalyzes directly into a jar file, while analyzing - when using version 2.8, if
sonar.java.binariesIn my case,$ {baseir} / release /) indicates a directory, the analysis is ok
what sonar.java.binaries The behavior of , implemented in 2.8, wanted? Or is this a regression?
Thanks,
Frederick
The form of your project Made using Maven, we recommend using it to analyze it. In that case you do not need to define sonar.java. * Properties
BTW: Better to upgrade directly to SonarCube 4.5.4 and Java plugin 3.3 to get all bug fixes / enhancements. New rules on bugs that come with the latest Java plugin:
Comments
Post a Comment