Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-355

Deploying from Leopard, with Svn 1.4.4 has error on automated Svn commit

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-beta-8
    • Component/s: scm
    • Labels:
      None
    • Number of attachments :
      0

      Description

      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESSFUL
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 3 minutes 25 seconds
      [INFO] Finished at: Fri Jan 11 08:49:42 PST 2008
      [INFO] Final Memory: 14M/29M
      [INFO] ------------------------------------------------------------------------
      [INFO] Checking in modified POMs...
      [INFO] Executing: svn --non-interactive commit --file /tmp/maven-scm-1359802395.commit --targets /tmp/maven-scm-28211-targets
      [INFO] Working directory: /scm/oss/jremoting/root/trunk
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Unable to commit files
      Provider message:
      The svn command failed.
      Command output:
      svn: Commit failed (details follow):
      svn: MKACTIVITY of '/jremoting/!svn/act/c136e17a-8ec7-44c4-a326-b2611ec72ffc': authorization failed (https://svn.codehaus.org)

        Issue Links

          Activity

          Hide
          Vincent Siveton added a comment -

          Sounds like svn authorization, not maven issue.

          Show
          Vincent Siveton added a comment - Sounds like svn authorization, not maven issue.
          Hide
          Matt Ryall added a comment -

          This is actually a Leopard issue, but there is a bug in Subversion for tracking it here:

          http://subversion.tigris.org/issues/show_bug.cgi?id=3059

          Show
          Matt Ryall added a comment - This is actually a Leopard issue, but there is a bug in Subversion for tracking it here: http://subversion.tigris.org/issues/show_bug.cgi?id=3059
          Hide
          Paul Hammant added a comment -

          I'm guessing there is going to be a standoff between the Svn team Tigris at Apple.

          Can the maven team work around it ? i.e. step back from --non-interactive for leopard users with a warning about it ?

          Or do we have to keep a Tiger Mac handy for deployments before this is resolved ?

          • Paul
          Show
          Paul Hammant added a comment - I'm guessing there is going to be a standoff between the Svn team Tigris at Apple. Can the maven team work around it ? i.e. step back from --non-interactive for leopard users with a warning about it ? Or do we have to keep a Tiger Mac handy for deployments before this is resolved ? Paul
          Hide
          Wendy Smoak added a comment -

          Brett managed to work around it by hacking the command line that gets executed, see:
          http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/

          Show
          Wendy Smoak added a comment - Brett managed to work around it by hacking the command line that gets executed, see: http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/
          Hide
          Dan Fabulich added a comment -

          I've filed SCM-402 to track this issue in the Maven SCM provider.

          Show
          Dan Fabulich added a comment - I've filed SCM-402 to track this issue in the Maven SCM provider.
          Hide
          Olivier Lamy added a comment -

          fix with upgrade to maven scm 1.1

          Show
          Olivier Lamy added a comment - fix with upgrade to maven scm 1.1
          Hide
          Benson Margulies added a comment -

          I just modified my POM to call for scm 1.1, and tried again, and got the same error. Can you give me any way to diagnose?

          Show
          Benson Margulies added a comment - I just modified my POM to call for scm 1.1, and tried again, and got the same error. Can you give me any way to diagnose?

            People

            • Assignee:
              Olivier Lamy
              Reporter:
              Paul Hammant
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: