It seems that the perforce consumer for the add command cannot parse the result it gets from perforce
//depot/sandboxes/mdelaney/utils/release-pom.xml#4 ? > Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - > opened for add > at org.apache.maven.scm.provider.perforce.command.add. > PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) Which perforce version do you use? maybe our maven-scm-provider-perforce is not compatible with the latest p4 version? Try to run the perforce commands the debug log shows you, or even better, try to build the perforce scm provider at your workstation (with -Ptck to run all the TCK tests). I have not looked at the p4 provider code yet, but there should be unit tests which have to fail on your computer. If not we have to add them ;) txs, strub --- Michael Delaney <[EMAIL PROTECTED]> schrieb am Mi, 11.6.2008: > Von: Michael Delaney <[EMAIL PROTECTED]> > Betreff: RE: Release plugin questions > An: "Maven Users List" <[email protected]> > Datum: Mittwoch, 11. Juni 2008, 17:45 > I executed the commands in the order below and still getting > the error. I have pasted the extended output below for your > review. > > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-7:prepare' > --> > [DEBUG] (f) addSchema = true > [DEBUG] (f) allowTimestampedSnapshots = false > [DEBUG] (f) autoVersionSubmodules = false > [DEBUG] (s) basedir = > C:\work\sandboxes\mdelaney\utils > [DEBUG] (f) commitByProject = false > [DEBUG] (f) dryRun = false > [DEBUG] (f) generateReleasePoms = true > [DEBUG] (f) password = [p4-password] > [DEBUG] (f) pomFileName = release-pom.xml > [DEBUG] (f) preparationGoals = clean verify > [DEBUG] (f) project = MavenProject: > proj:proj-utils:1.2-SNAPSHOT @ > C:\work\sandboxes\mdelaney\utils\pom.xml > [DEBUG] (f) reactorProjects = [MavenProject: > proj:proj-utils:1.2-SNAPSHOT @ > C:\work\sandboxes\mdelaney\utils\pom.xml] > [DEBUG] (f) resume = true > [DEBUG] (f) scmCommentPrefix = [maven-release-plugin] > [DEBUG] (f) settings = > [EMAIL PROTECTED] > [DEBUG] (f) updateDependencies = true > [DEBUG] (f) useEditMode = false > [DEBUG] (f) username = [p4-username] > [DEBUG] -- end configuration -- > [INFO] [release:prepare] > [DEBUG] release.properties not found - using empty > properties > [INFO] Verifying that there are no local modifications... > [DEBUG] SCM path in pom: //depot/sandboxes/mdelaney/utils > [DEBUG] Executing: p4 -p localhost:1666 -u [p4-username] -P > ******** where > C:\work\sandboxes\mdelaney\utils\pom.xml > [DEBUG] //depot/sandboxes/mdelaney/utils/pom.xml > //mdelaney-default/sandboxes/mdelaney/utils/pom.xml > c:\work\sandboxes\mdelaney\utils\pom.xml > [DEBUG] Actual POM location: > //depot/sandboxes/mdelaney/utils > [DEBUG] Executing p4 -d > C:\work\sandboxes\mdelaney\utils -p > localhost:1666 -u [p4-username] -P ******** opened > //depot/sandboxes/mdelaney/utils/... > [INFO] Checking dependencies and plugins for snapshots ... > [INFO] Transforming 'Proj Utils'... > [DEBUG] No SCM translator found - skipping rewrite > [DEBUG] Executing p4 -d > C:\work\sandboxes\mdelaney\utils -p > localhost:1666 -u [p4-username] -P ******** edit pom.xml > [INFO] Generating release POMs... > [INFO] Generating release POM for 'Proj Utils'... > [DEBUG] No SCM translator found - skipping rewrite > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Cannot add release POM to SCM: Exception while > executing SCM command. > > Unknown input: > //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened > for add > [INFO] > ------------------------------------------------------------------------ > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: > Cannot add release POM to SCM: Exception while executing > SCM command. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at > org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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: > Cannot add release POM to SCM: Exception while executing > SCM command. > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:140) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: > org.apache.maven.shared.release.ReleaseExecutionException: > Cannot add release POM to SCM: Exception while executing > SCM command. > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addReleasePomsToScm(GenerateReleasePomsPhase.java:197) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.generateReleasePoms(GenerateReleasePomsPhase.java:133) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execute(GenerateReleasePomsPhase.java:106) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execute(GenerateReleasePomsPhase.java:93) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) > at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:136) > ... 18 more > Caused by: org.apache.maven.scm.ScmException: Exception > while executing SCM command. > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:62) > at > org.apache.maven.scm.provider.perforce.PerforceScmProvider.add(PerforceScmProvider.java:167) > at > org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProvider.java:145) > at > org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProvider.java:125) > at > org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addReleasePomsToScm(GenerateReleasePomsPhase.java:188) > ... 25 more > Caused by: java.lang.IllegalStateException: Unknown input: > //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened > for add > at > org.apache.maven.scm.provider.perforce.command.add.PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) > at > org.apache.maven.scm.provider.perforce.command.add.PerforceAddCommand.executeAddCommand(PerforceAddCommand.java:63) > at > org.apache.maven.scm.command.add.AbstractAddCommand.executeCommand(AbstractAddCommand.java:45) > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) > ... 29 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 10 seconds > [INFO] Finished at: Wed Jun 11 11:27:54 EDT 2008 > [INFO] Final Memory: 8M/127M > [INFO] > ------------------------------------------------------------------------ > > > > -----Original Message----- > From: Bracewell, Robert [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 11, 2008 5:12 AM > To: Maven Users List > Subject: RE: Release plugin questions > > Try the following command sequence to ensure your > environment is clean: > mvn -e -X release:clean clean > mvn -e -X release:prepare -DdryRun=true > mvn -e -X release:clean clean > mvn -e -X release:prepare > > The -e and -X should hopefully give some more output re > error conditions > > -----Original Message----- > From: Michael Delaney [mailto:[EMAIL PROTECTED] > Sent: 10 June 2008 17:01 > To: Maven Users List > Subject: RE: Release plugin questions > > Sorry, I am still getting the same error when I add that to > the pom.xml file. > > -----Original Message----- > From: Bracewell, Robert [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 10, 2008 11:28 AM > To: Maven Users List > Subject: RE: Release plugin questions > > Try specifying the developerConnection, e.g., > > <!-- P4 Location --> > > <scm> > > > <connection>scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils</connection> > > > <developerConnection>scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils</developerConnection> > > </scm> > > > > -----Original Message----- > From: Michael Delaney [mailto:[EMAIL PROTECTED] > Sent: 10 June 2008 15:20 > To: Maven Users List > Subject: RE: Release plugin questions > > > > Yes, it does have the scm section, as defined by > http://maven.apache.org/scm/perforce.html. > > > > <project> > > ... > > <scm> > > <connection> > > > scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils > > </connection> > > </scm> > > ... > > </project> > > > > -----Original Message----- > > From: Mark Struberg [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 10, 2008 10:15 AM > > To: Maven Users List > > Subject: AW: Release plugin questions > > > > Is your pom.xml having a <scm> section? > > > > Releasing also tags the version in your scm, so you have to > tell maven the SCM repository it uses. > > > > LieGrü, > > strub > > > > > > --- Michael Delaney <[EMAIL PROTECTED]> schrieb > am Di, 10.6.2008: > > > > > Von: Michael Delaney <[EMAIL PROTECTED]> > > > Betreff: Release plugin questions > > > An: "Maven Users List" > <[email protected]> > > > Datum: Dienstag, 10. Juni 2008, 15:29 > > > All, > > > > > > > > > > > > I am trying to evaluate the maven-release-plugin > (version > > > 2.0-beta-7) > > > and I can't seem to get it to work flawlessly. > Here is > > > my scenario: I > > > have a single library/artifact that has zero > dependencies. > > > The current > > > version is set to 1.2-SNAPSHOT in the pom.xml file > (see > > > below for XML > > > elements). However, when I go to run release:prepare I > get > > > the error > > > pasted below. The Perforce path is valid and the user > has > > > the proper > > > rights to edit the file (verified via Perforce UI and > > > command-line). > > > > > > > > > > > > What am I doing wrong? > > > > > > > > > > > > [POM Elements] > > > > > > <project ... > > > > > > > > <modelVersion>4.0.0</modelVersion> > > > > > > > <artifactId>proj-utils</artifactId> > > > > > > <packaging>jar</packaging> > > > > > > > <version>1.2-SNAPSHOT</version> > > > > > > <name>Project Utilities</name> > > > > > > > <url>http://www.mydomain.com</url> > > > > > > <groupId>proj</groupId> > > > > > > > > > > > > [Maven Error] > > > > > > [INFO] [release:prepare] > > > > > > [INFO] Resuming release from phase > > > 'generate-release-poms' > > > > > > [INFO] Generating release POMs... > > > > > > [INFO] Generating release POM for 'Lty > Utils'... > > > > > > [DEBUG] No SCM translator found - skipping rewrite > > > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > [ERROR] BUILD ERROR > > > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > [INFO] Cannot add release POM to SCM: Exception while > > > executing SCM > > > command. > > > > > > > > > > > > Unknown input: > > > //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - > > > opened for add > > > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > [DEBUG] Trace > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: > > > Cannot add > > > release POM to SCM: Exception while executing SCM > command. > > > > > > > __________________________________________________________ > > Gesendet von Yahoo! Mail. > > Dem pfiffigeren Posteingang. > > http://de.overview.mail.yahoo.com > > > > --------------------------------------------------------------------- > > 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] __________________________________________________________ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
