You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-users@maven.apache.org by Bruno Dumant <bd...@businessobjects.com> on 2006/10/02 18:46:19 UTC
Problem checking-in files with perforce
Hi,
I cannot succeed in submitting anything on perforce using maven. This is
what I get when I running release:prepare:
[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-commit-release'
[INFO] Checking in modified POMs...
[DEBUG] Executing p4 -H <my server>:<my port> submit -
i
[DEBUG] Sending changelist:
Change: new
Description:
[maven-release-plugin] prepare release Labs.GraphicsMasher-1.3.3
Files:
//labs/GraphicsServer/Stable/GraphServer/masher/pom.xml
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
Unable to submit
Command output:
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to commit files
Provider message:
Unable to submit
Command output:
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:555)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:219)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to
commit files
Provider message:
Unable to submit
Command output:
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
leaseMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 16 more
I have the same kind of output when I just try to commit a file. What is
strange is that updates (scm:update) correctly work: in particular, a
client spec is properly created and everything runs smoothly. When
trying to submit files, no client spec seems to be created. Is it the
normal behaviour?
Thanks for any hint!
Bruno
Re: Problem checking-in files with perforce
Posted by Yuri Schimke <yu...@gmail.com>.
Hi,
This is a stopgap answer, until a definitive answer from the Perforce guys.
Some of the tasks generate a new clientspec, but a lot of the others use an
existing one.
The main thing to check is that your command line p4 works as expected from
that directory. If not you will either need to set the P4* environment
variables, or if you use multiple clientspecs on your machine use the
P4CONFIG setup.
On 10/2/06, Bruno Dumant <bd...@businessobjects.com> wrote:
>
> Hi,
>
>
>
> I cannot succeed in submitting anything on perforce using maven. This is
> what I get when I running release:prepare:
>
>
>
> [INFO] [release:prepare]
>
> [INFO] Resuming release from phase 'scm-commit-release'
>
> [INFO] Checking in modified POMs...
>
> [DEBUG] Executing p4 -H <*my server*>:<*my port*> submit -
>
> i
>
> [DEBUG] Sending changelist:
>
> Change: new
>
>
>
> Description:
>
> [maven-release-plugin] prepare release Labs.GraphicsMasher-1.3.3
>
>
>
> Files:
>
> //labs/GraphicsServer/Stable/GraphServer/masher/pom.xml
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Unable to commit files
>
> Provider message:
>
> Unable to submit
>
> Command output:
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [DEBUG] Trace
>
> org.apache.maven.BuildFailureException: Unable to commit files
>
> Provider message:
>
> Unable to submit
>
> Command output:
>
>
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>
> ultLifecycleExecutor.java:555)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
>
> Goal(DefaultLifecycleExecutor.java:488)
>
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (Defau
>
> ltLifecycleExecutor.java:458)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>
> dleFailures(DefaultLifecycleExecutor.java:306)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>
> ts(DefaultLifecycleExecutor.java:219)
>
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLi
>
> fecycleExecutor.java:140)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
>
> java:39)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
>
> sorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
>
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> :315)
>
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>
> at org.codehaus.classworlds.Launcher.mainWithExitCode(
> Launcher.java:430)
>
>
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
>
> Provider message:
>
> Unable to submit
>
> Command output:
>
>
>
> at org.apache.maven.plugins.release.PrepareReleaseMojo.execute
> (PrepareRe
>
> leaseMojo.java:114)
>
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPlugi
>
> nManager.java:412)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>
> ultLifecycleExecutor.java:534)
>
> ... 16 more
>
>
>
> I have the same kind of output when I just try to commit a file. What is
> strange is that updates (scm:update) correctly work: in particular, a client
> spec is properly created and everything runs smoothly. When trying to submit
> files, no client spec seems to be created. Is it the normal behaviour?
>
>
>
> Thanks for any hint!
>
>
>
> Bruno
>
>
>
--
Yuri Schimke