-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent confusion with the commercial plugin #1
Comments
Thank you @Stephan202 ! I forgot to check that... Gilles |
👍 |
Is there a reason you don't close this ticket? It's not only a matter of confusion regarding the aforementioned information: if you automatically update your plugin, the downloaded file is actually https://sonarsource.bintray.com/CommercialDistribution/sonar-swift/sonar-swift-plugin-1.5.1.jar (from http://www.sonarsource.com/products/plugins/languages/swift/). The result is that you wipe out your plugin and install the commercial one! :-) |
Hi |
octo-technology/sonar-objective-c#88 There was a similar Problem with sonar objective-c |
Ok, So, I just need to change the language key and few other things. Your ideas are welcomed ! |
swift-ce ? |
swiftos (for open source), You're welcome! ;P |
Hi, I changed everything as detailed in PR octo-technology/sonar-objective-c#88. But still the confusion remains in the update center.... Any ideas ? |
Finally fixed ! It is available in release 0.2.2 |
…aster * commit '1702d264a3aed8792cacda9d11c8a94bc2f4972d': Moved the project to gradle
I just dropped
sonar-swift-plugin-0.1.jar
into our SonarQube 5.2 installation. It's recognized just fine, quality profiles and rules and all, which is nice :). (Can't give feedback on analysis results yet; I'm not involved in Swift development in our company, and I haven't communicated yet that I installed this plugin.)But when I go to the Update Center, it suggests that I upgrade the plugin from version 0.1 to 1.5, with a link to the home page and release notes of the commercially available/official Swift plugin. That's quite confusing, and probably not what you want. :)
The text was updated successfully, but these errors were encountered: