Details

    • Number of attachments :
      0

      Description

      I have setup the scm plugin with the credentials in the sonar configuration. When I now run sonar:sonar on a different machine, the credentials on this local machine in folder $HOME/.subversion/auth will be overwritten with the credentials from the sonar server. You can simply discover this by:

      1) move $HOME/.subversion/auth to $HOME/.subversion/copy_auth
      2) execute mvn clean install sonar:sonar
      3) check $HOME/.subversion/

      You will recognise, that the auth folder will be created from the scm plugin with the credentials from the sonar server.

        Issue Links

          Activity

          Hide
          Evgeny Mandrikov added a comment -

          I didn't checked this yet, but this issue looks similar to SCM-562, so should be fixed with upgrade to Maven SCM 1.4 (SONARPLUGINS-413).

          Show
          Evgeny Mandrikov added a comment - I didn't checked this yet, but this issue looks similar to SCM-562 , so should be fixed with upgrade to Maven SCM 1.4 ( SONARPLUGINS-413 ).
          Hide
          Evgeny Mandrikov added a comment -

          Hi Cyrill,

          Do you use Pure Jave implementation or not?

          Show
          Evgeny Mandrikov added a comment - Hi Cyrill, Do you use Pure Jave implementation or not?
          Hide
          Cyrill Ruettimann added a comment -

          I used the default implementation (configuration option)

          Show
          Cyrill Ruettimann added a comment - I used the default implementation (configuration option)
          Hide
          Cyrill Ruettimann added a comment -

          Ah, just received the notification that scm 1.4 is out now

          Show
          Cyrill Ruettimann added a comment - Ah, just received the notification that scm 1.4 is out now
          Hide
          Evgeny Mandrikov added a comment -

          Yes - I know about release, but now I'm not sure that problem comes from SCM 1.3. I think it comes from maven-scm-provider-svnjava (http://code.google.com/p/maven-scm-provider-svnjava/) and more accurately from svnkit. So, could you please set property "sonar.scm-activity.prefer_pure_java" to false and see if problem dissapear?

          Show
          Evgeny Mandrikov added a comment - Yes - I know about release, but now I'm not sure that problem comes from SCM 1.3. I think it comes from maven-scm-provider-svnjava ( http://code.google.com/p/maven-scm-provider-svnjava/ ) and more accurately from svnkit. So, could you please set property "sonar.scm-activity.prefer_pure_java" to false and see if problem dissapear?
          Hide
          Evgeny Mandrikov added a comment -

          Cyrill, did you tried what I've suggested in previous comment ?

          Show
          Evgeny Mandrikov added a comment - Cyrill, did you tried what I've suggested in previous comment ?
          Hide
          Evgeny Mandrikov added a comment -

          Looks like problem with maven-scm-provider-svnjava was fixed in version 1.12

          Show
          Evgeny Mandrikov added a comment - Looks like problem with maven-scm-provider-svnjava was fixed in version 1.12

            People

            • Assignee:
              Evgeny Mandrikov
              Reporter:
              Cyrill Ruettimann
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: