Conflict with Sonarsource C/C++/Objective C plugin

[jfisbein]

Sonarsource has a commercial C/C++/Objective C plugin, if you install the Sornarsource plugin it takes precedence even if you only have the license for the C/C++ functionalities (not for Objective C).

It looks like the problem is because both plugins (Octo & SonarSource) share the same key "objc" and conflicts.

Does it make sense to change the key to something like "octo-objc" ?

[cyrilpicat]

ok, thanks for the report.

I have to check the impacts on the history, but it makes sense to change to something else, right?

"objective-c" might be a better idea, isn't it?

[jfisbein]

Yes, anything but "objc" should be ok. :-)

[agigleux]

To complete the demand of @jfisbein in order to use both plugins in the same SQ instance and choose which plugin to activate we can force the sonar.language property but both plugins are using the same language's key = objc so indeed would be great to change "objc" in src/main/java/org/sonar/plugins/objectivec/core/ObjectiveC.java to something else.

[mjdetullio]

I was worried changing this would have really adverse effects on project data, but it seems the only thing you really lose is your quality profiles so that's not too bad.

[mjdetullio]

Fixed in PR #97

[rodrigoturnes]

How can I change the key then? I am running Octo and getting the "Caused by: No license for objc" error.

Thanks!

[mjdetullio]

You have to build PR #97 from source and then change your key from objc to objectivec

[rodrigoturnes]

Wow, seems to be a lot of re-work! Is there any chance of uninstalling SonarSource plugin in order to give precedence to Octo?

[mjdetullio]

Yes, uninstalling one of the plugins will remove the conflict.

[rodrigoturnes]

Which is the proper way to uninstall SonarSource plugin? Been trying to achieve this but couldn't...

[rodrigoturnes]

Solved the issue, switched plugins and worked.

Thanks for your help!