Details

    • Number of attachments :
      0

      Description

      Evgeny Mandrikov (mandrikov@gmail.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 (fabrice.bellingard@sonarsource.com)
      12/05/13
      To: dev@sonar.codehaus.org

      Hi John,

      Cloudbees jobs indeed deploys built artifacts on it repository, but in your case it is located here:

      http://repository-sonarplugins.forge.cloudbees.com/snapshot/com/wrightfully/sonar-plugins/dotnet/resharper/

      , because you haven't used the "standard" groupId for forge plugins.

      Best regards,

      Fabrice BELLINGARD | SonarSource
      http://sonarsource.com

      John M. Wright
      11/30/13
      To: dev@sonar.codehaus.org

      SonarSource gurus:

      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.

      From http://docs.codehaus.org/plugins/servlet/mobile#content/view/120258992:

      "
      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/)

      Thanks
      ~john

        Activity

        Show
        John Wright added a comment - https://github.com/SonarCommunity/sonar-dotnet-resharper/commit/b0c152600b157e0652569db114b23ee901ba7b05

          People

          • Assignee:
            John Wright
            Reporter:
            John Wright
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: