Mike,

thanks for the help !

I ran maven -X scm:update --> it was now successful (see trace below) !
I don't understand what happened :o(
Could you please give some explanations about the log ?
Did I run it with a newer plug-in version ?

Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -X scm:update
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und
Einstellungen\Tevan\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'd:\tools\maven-2.0.1\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[DEBUG] maven-scm-plugin: resolved to version 1.0-beta-2 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
[INFO] ---------------------------------------------------------------------
-------
[INFO] Building Maven Webapp Archetype
[INFO]    task-segment: [scm:update] (aggregator-style)
[INFO] ---------------------------------------------------------------------
-------
[DEBUG] org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-settings:jar:2.0
[DEBUG]   org.apache.maven:maven-settings:jar:2.0 (selected for runtime)
[DEBUG]     org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG]     org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG]       classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG]       junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-model:jar:2.0
[DEBUG]     org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-cvs:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-api:jar:1.0-beta-2
[DEBUG]     org.apache.maven.scm:maven-scm-api:jar:1.0-beta-2 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-local:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-local:jar:1.0-beta-2
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-starteam:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-manager-plexus:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-managers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-containers:pom:1.0
[DEBUG]     plexus:plexus-container-default:jar:1.0-alpha-5 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-utils:jar:1.0.1
[DEBUG]       plexus:plexus-utils:jar:1.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-clearcase:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-perforce:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-2
(selected for runtime)
[DEBUG]     regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-plugin-api:jar:2.0
[DEBUG]   org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-svn:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-scm-plugin:1.0-beta-2:update' -->
[DEBUG]   (f) basedir = D:\p4client\components\ecb-presentation-tiles
[DEBUG]   (f) connectionUrl =
scm:perforce:[EMAIL PROTECTED]:1666://components/ecb-presentation-tiles
[DEBUG]   (f) settings = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [scm:update]
[DEBUG] Updating clientspec:
Client: Tevan-ECB-maven
Root:
        D:\p4client\components\ecb-presentation-tiles
View:
        //components/ecb-presentation-tiles/... //Tevan-ECB-maven/...

[DEBUG] Consuming: Client Tevan-ECB-maven saved.
[DEBUG] Executing p4 -H ECB:1666 -u ecb -cTevan-ECB-maven sync ...
[DEBUG] Consuming: //components/ecb-presentation-tiles/pom.xml#2 - added as
D:\p4client\components\ecb-presentation-tiles\pom.xml
[DEBUG] Consuming:
//components/ecb-presentation-tiles/src/main/webapp/index.jsp#1 - added as
D:\p4client\components\ecb-presentation-tiles\src\main\webapp\inde
x.jsp
[DEBUG] Consuming:
//components/ecb-presentation-tiles/src/main/webapp/WEB-INF/web.xml#1 -
added as D:\p4client\components\ecb-presentation-tiles\src\main\webap
p\WEB-INF\web.xml
[INFO] ---------------------------------------------------------------------
-------
[INFO] BUILD SUCCESSFUL
[INFO] ---------------------------------------------------------------------
-------
[INFO] Total time: 5 seconds
[INFO] Finished at: Tue Feb 07 20:07:32 CET 2006
[INFO] Final Memory: 3M/5M
[INFO] ---------------------------------------------------------------------
-------

D:\p4client\components\ecb-presentation-tiles>maven scm:update
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] ---------------------------------------------------------------------
-------
[INFO] Building Maven Webapp Archetype
[INFO]    task-segment: [scm:update] (aggregator-style)
[INFO] ---------------------------------------------------------------------
-------
[INFO] [scm:update]
[INFO] ---------------------------------------------------------------------
-------
[INFO] BUILD SUCCESSFUL
[INFO] ---------------------------------------------------------------------
-------
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Feb 07 20:09:15 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] ---------------------------------------------------------------------
-------



-----Ursprüngliche Nachricht-----
Von: Mike Perham [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 18:16
An: Maven Users List
Betreff: RE: AW: AW: m2 and perforce ???


"Unable to sync" usually indicates the user is not logged in.  Obviously
that sounds like that is not the case here.

Esteban, turn on debugging with -X and send me the relevant output directly
in email please.

mike


-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 10:50 AM
To: Maven Users List
Subject: Re: AW: AW: m2 and perforce ???

I don't know, i never used Perforce.

Mike, any idea?

Emmanuel

Esteban Chavez a écrit :
> I suppose, I'm logged in.
> Otherwise 'p4 sync -f" would produce an error, isn't it ?
> Is there a command to test if the used user is logged in ?
>
> Further, I ran the following goal
>
> maven -e scm:update -Dusername=ecb -Dpassword=MY_PASSWD --> NOK
>
>
> "p4 info" returned :
>
> D:\p4client\components\ecb-presentation-tiles>p4 info User name: ecb
> Client name: ECB Client host: ECB Client root: D:\p4client\components
> Current directory: d:\p4client\components\ecb-presentation-tiles
> Client address: 127.0.0.1:3730
> Server address: localhost:1666
> Server root: C:\Programme\Perforce
> Server date: 2006/02/07 12:10:03 +0100 Westeuropõische Normalzeit
> Server version: P4D/NTX86/2003.2/62096 (2004/06/08) Server license:
> none
>
> Is it possible that the problem is caused by my perforce version ? I
> don't have any license, it's a single user installation (for free).
>
> Thanks, Emmanuel !
>
> Esteban.
>
>
> -----Ursprüngliche Nachricht-----
> Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 7. Februar 2006 11:31
> An: Maven Users List
> Betreff: Re: AW: m2 and perforce ???
>
>
> Are you logged in to Perforce?
>
> I think perforce provider requires that you're logged in.
>
> Emmanuel
>
> Esteban Chavez a écrit :
>
>>Hi Emmanuel,
>>
>>This is what I get when running the update goal. ('maven' is my own
>>alias for 'mvn') Esteban.
>>
>>
>>D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
>>+ Error stacktraces are turned on.
>>[INFO] Scanning for projects...
>>[INFO] Searching repository for plugin with prefix: 'scm'.
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[INFO] Building Maven Webapp Archetype
>>[INFO]    task-segment: [scm:update] (aggregator-style)
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[INFO] [scm:update]
>>[ERROR] Provider message:
>>[ERROR] Unable to sync
>>[ERROR] Command output:
>>[ERROR]
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[ERROR] BUILD ERROR
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[INFO] Command failed.
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[INFO] Trace
>>org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> ltLife
>
>>cycleExecutor.java:555)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG
> oal(De
>
>>faultLifecycleExecutor.java:485)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul
> tLifec
>
>>ycleExecutor.java:455)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> leFail
>
>>ures(DefaultLifecycleExecutor.java:303)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(Defa
>
>>ultLifecycleExecutor.java:216)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ecycle
>
>>Executor.java:139)
>>        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:249)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39
>
>>)
>>        at
>>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl
>
>>.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.MojoExecutionException: Command failed.
>>        at
>>
>
> org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMoj
> o.java
>
>>:252)
>>        at
>>org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
>>        at
>>
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin
> Manage
>
>>r.java:432)
>>        at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> ltLife
>
>>cycleExecutor.java:530)
>>        ... 16 more
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>[INFO] Total time: 4 seconds
>>[INFO] Finished at: Tue Feb 07 10:55:07 CET 2006 [INFO] Final Memory:
>>3M/6M
>>
>
> [INFO]
> ---------------------------------------------------------------------
>
>>-------
>>
>>
>>
>>
>>-----Ursprüngliche Nachricht-----
>>Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
>>Gesendet: Dienstag, 7. Februar 2006 10:44
>>An: Maven Users List
>>Betreff: Re: m2 and perforce ???
>>
>>
>>Do you have an error or something?
>>
>>Emmanuel
>>
>>Esteban Chavez a écrit :
>>
>>
>>>Hi,
>>>
>>>is there someone who got already m2 and perforce running together ?
>>>I'm unable to make a source update (mvn -e scm:update)
>>>
>>>mvn -e scm:status --> is ok
>>>mvn -e scm:validate --> is ok
>>>
>>>"p4 sync -f" --> is ok
>>>
>>>Thank you very much !
>>>
>>>Esteban.
>>>
>>>
>>>Esteban Chávez Baroni
>>>banking objects
>>>
>>>Moorweg 8
>>>22453 Hamburg
>>>Phone: +49 -(0)40 - 57006757
>>>Mobile: +49 -(0)163 -5813639
>>>Mail: [EMAIL PROTECTED]
>>>Web: www.banking-objects.de
>>>
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>---
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to