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

Maven 2.x Release Plugin

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

Created: 11/Jan/08 03:22 PM Updated: Monday 06:32 PM

Component/s:

scm

Affects Version/s:

None

Fix Version/s:

2.0-beta-8

Time Tracking:

Not Specified

Issue Links:

dependent

This issue depends upon:

~~SCM-402~~ scm:checkin doesn't work on OS X 10.5 Leopard

~~MRELEASE-369~~ upgrade scm version to last 1.1 (and add by default new providers accurev and git)

Description

« Hide

[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)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Vincent Siveton added a comment - 15/Jan/08 10:01 PM

Sounds like svn authorization, not maven issue.

[ Permlink | « Hide ]

Matt Ryall added a comment - 10/Mar/08 06:39 PM

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

[ Permlink | « Hide ]

Paul Hammant added a comment - 15/Mar/08 08:09 PM

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

[ Permlink | « Hide ]

Wendy Smoak added a comment - 15/Mar/08 08:14 PM

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/

[ Permlink | « Hide ]

Dan Fabulich added a comment - 19/Aug/08 01:40 PM

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

[ Permlink | « Hide ]

Olivier Lamy added a comment - 27/Aug/08 11:00 AM

fix with upgrade to maven scm 1.1

[ Permlink | « Hide ]

benson margulies added a comment - 01/Dec/08 06:32 PM

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?