[MRELEASE-355] Deploying from Leopard, with Svn 1.4.4 has error on automated Svn commit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta-8
• Component/s: scm
• Assignee: Olivier Lamy
• Reporter: Paul Hammant
• Created: 11/Jan/08 15:22
• Updated: 06/Apr/15 01:08
• Resolved: 27/Aug/08 11:00

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

• depends upon: SCM-402 scm:checkin doesn't work on OS X 10.5 Leopard
• depends upon: MRELEASE-369 upgrade scm version to last 1.1 (and add by default new providers accurev and git)