The error handling in the perforce scm plugin was minimal so I went
ahead and patched it in my local repository so I could test. My patch
(http://jira.codehaus.org/browse/SCM-363) has been applied to the trunk
so if you install it locally you should be able to get more information.
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-s
cm-provider-perforce/
http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/mave
n-scm-provider-perforce/
Also I have to manually login once per day since we have ticket-based
authorization and the maven-scm-provider for perforce doesn't handle
logins and assumes you have logged in manually.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Carl Pettersson
Sent: Tuesday, June 17, 2008 6:56 AM
To: scm-users@maven.apache.org
Subject: Perforce "Unable to submit" error
Hello!
I'm having trouble getting scm with perforce working. I've set up a
simple project (archetype:create), and then modified my pom.xml to
contain this:
...
scm:perforce:p4bck:1666://my-app
scm:perforce:p4bck:1666://my-app
...
org.apache.maven.plugins
maven-scm-plugin
maven.scm.perforce.clientspec.name
Mavenclient
user
passwd
developerConnection
...
I am able to do scm:update without errors, and the p4 commandline client
works. However, if I do any action which tries to submits, such as
release:prepare or scm:checkin, I get an "Unable to submit" error. For
example, here I try checking in my pom.xml:
[DEBUG] Executing p4 -d C:\PerforceRoot\MC\my-app -p p4bck:1666 -u user
-P submit -i
[DEBUG] SCM path in pom: //my-app
[DEBUG] Executing: p4 -p p4bck:1666 -u user -P where
C:\PerforceRoot\MC\my-app\pom.xml
[DEBUG] cannot find depot => using //my-app
[DEBUG] Sending changelist:
Change: new
Description:
mvn
Files:
//my-app/pom.xml
[ERROR] Provider message:
[ERROR] Unable to submit
[ERROR] Command output:
[ERROR]
First sign of something not working I suppose is "cannot find depot",
why? And when it cannot, it still uses the correct one... (I've also
tried using //Mavenclient/my-app as url, only difference is that it
falls back to using //Mavenclient/my-app instead of //my-app)
The Mavenclient clientspec exists.
I'm using Maven version 2.0.9 with JDK 1.5.0.15 on WinXP. scm-plugin is
version 1.0, release-plugin is 2.0-beta-7.
Have I done some misconfiguration? There are a few threads about this
available when googling, however they either don't get a reply, or the
solution does not solve the problem.
Any other information needed to debug this?
Thankful for any help
Carl Pettersson