Evgeny Mandrikov (email@example.com)
To: Sonar Developers List
This is not just "standard" - due to current groupId you won't be able to upload artifacts into Maven Central repository thru SonarQube forge, because uploads are restricted to "org.codehaus.sonar-plugins". Thus formally you won't be able to finalize release.
Fabrice Bellingard (firstname.lastname@example.org)
Cloudbees jobs indeed deploys built artifacts on it repository, but in your case it is located here:
, because you haven't used the "standard" groupId for forge plugins.
Fabrice BELLINGARD | SonarSource
John M. Wright
The plugin release page on JIRA states that GutHub-based (forge) plugins should have their artifacts published to a known location, but I'm not seeing my sonar-dotnet-resharper there.
Github, then the artifact is automatically deployed by Cloudbees Jenkins tohttp://repository-sonarplugins.forge.cloudbees.com/snapshot/org/codehaus/sonar-plugins.
As I'm preparing to call for a release vote on this plugin, do I need to do something to have it added here, or is it sufficient to just point to the "lastBuild" artifact in Jenkins? (https://sonarplugins.ci.cloudbees.com/job/dotnet-resharper/lastBuild/com.wrightfully.sonar-plugins.dotnet.resharper$sonar-dotnet-resharper-plugin/)