[NEW PLUGIN] Magik - Requesting inclusion in SonarQube Marketplace

Hi. I would like to share a plugin that helps to analyse code quality for Magik

Hi,

Welcome to the community!

Going through the bureaucratic requirements, the plugin fails #3.5:

  1. The key of your plugin must be:

    5. not just the name of a language (e.g. cannot be java, rust, js/javascript, …)
    examples of good keys: motionchart, communityphp, scmactivity

Also, can you give me a project to test with?

 
Ann

I could change the pluginKey to communitymagik for example, but then the pom.xml in the GitHub repository would not be aligned anymore.

Some example projects:

Hi,

Yes, you would need to make a change in the plugin pom. Either you’ll need to change the artifactId or add a sonar.pluginKey property.

 
HTH,
Ann

I see there is already an artifactId in the pom.xml (sonar-magik-plugin). Would that be a good name as well?

Hi,

Yes, declaring an artifact ID is part of Maven development.

Please see the link in my previous post for how artifact IDs are translated to plugin keys.

 
Ann

I opened a PR, Be compliant for publish to SonarQube Marketplace by sebastiaanspeck · Pull Request #292 · StevenLooman/magik-tools · GitHub, but when looking at for example the Delphi plugin, I see they changed the general pluginKey: sonar-delphi/sonar-delphi-plugin/pom.xml at 919bbac881d2c68a2afcec59c027409408d4b946 · integrated-application-development/sonar-delphi · GitHub

Edit: updated the general pluginKey property in the pom.xml

Hi,

Please come back to me when we’re in a state to proceed.

Also, I still need a project to test with.

 
Ann

Will do.

Two projects you can use to test with:

Please close this topic. The owner of this plugin doesn’t want to have it published to SQ Marketplace

Hi,

I’m sorry to hear (read) that. I had assumed that since you were a committer on that repo this was done in collaboration with the owner.

Feel free to come back here if anything changes.

 
Ann