ERROR: The rule 'OCLint:compiler warning' does not exist.

Question

ERROR: The rule 'OCLint:compiler warning' does not exist.

andrewclaus opened this issue 7 years ago · 11 comments

INFO: Sensor org.sonar.plugins.objectivec.violations.oclint.OCLintSensor
INFO: Processing OCLint report sonar-reports/oclint_report.xml
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 8.993s
INFO: Final Memory: 49M/321M
INFO: ------------------------------------------------------------------------
ERROR: Error during SonarQube Scanner execution
ERROR: The rule 'OCLint:compiler warning' does not exist.

Any ideas what might be causing this? SonarQube 5.6

UPDATE: with some testing, OCLint 0.13 has this error, while OCLint 0.12 does not. Is there a new compiler warning that was introduced in 0.13 that does not yet exist in this sonar plugin?

Answer 1 · 2017-11-27T08:18:23.000Z

@andrewclaus any updates?

Answer 2 · 2017-11-27T15:17:00.000Z

@CoreOne23 I ended up downgrading OCLint to 0.12 for now.

Answer 3 · 2017-11-27T15:49:05.000Z

Oh, k. I just deleted the 'compiler warning' errors from oclint.xml in my file project folder. They were just warnings(like uipopovercontroller depreciated..), not errors. Now the analysis could work with 0.13 version. Waiting for the real solution. :(

Answer 4 · 2017-12-06T08:27:52.000Z

Hi @CoreOne23,

I updated OCLint rules fir 0.13 support in the version 0.6.2 of the plugin.
Could you test again and tell me if it is okay ?

Gilles.

Answer 5 · 2017-12-07T20:57:33.000Z

Hi ,

It appears Clang ruleset violations are not mapped.

For example:

'MPMoviePlayerController' is deprecated: first deprecated in iOS 9.0 - Use AVPlayerViewController in AVKit.

Will result in ERROR: The rule 'OCLint:compiler warning' does not exist.

I'm wonder if that means OCLint 0.13 is defaulting to -enable-clang-static-analyzer?

Answer 6 · 2018-01-11T01:24:15.000Z

As a workaround you can edit your run-sonar.sh in the mean time to add:

-extra-arg=-Wno-everything

To the oclint-json-compilation-database command. Your final command should look like:

oclint-json-compilation-database -v -- -extra-arg=-Wno-everything -rc LONG_LINE=250 -max-priority-1 100000 -max-priority-2 100000 -max-priority-3 100000 -report-type pmd -o sonar-reports/oclint.xml

This will disable compiler warnings from being generated however.

Answer 7 · 2018-02-01T16:46:39.000Z

Thanks @keithpk ! Looks like a good workaround for now

Answer 8 · 2018-08-15T07:59:46.000Z

@zippy1978 It's not okey! I had update to the latest version for sonar-objective-c. But also
have the same issue

Answer 9 · 2018-08-31T08:31:22.000Z

Hi @zippy1978 ,
I removed the obj C plugin and installed https://github.com/Backelite/sonar-swift/releases/tag/0.4.0, Still getting the compiler warning error. As I said earlier, I'm still deleting the compiler warning from xml to run the scanning successful.

Answer 10 · 2018-08-31T09:23:23.000Z

-extra-arg=-Wno-everything - still giving me the error.

Answer 11 · 2018-08-31T15:59:24.000Z

@CoreOne23 If you are using the newest version of the swift/Objective-C plugin, make sure you have OCLint 0.13 (or if you have 0.13, maybe try downgrading to 0.12).