maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <>
Subject [jira] Closed: (MRELEASE-155) Multiproject Release Fails on Windows
Date Wed, 21 Mar 2007 20:48:34 GMT


Emmanuel Venisse closed MRELEASE-155.

      Assignee: Emmanuel Venisse
    Resolution: Duplicate

> Multiproject Release Fails on Windows
> -------------------------------------
>                 Key: MRELEASE-155
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: scm
>    Affects Versions: 2.0-beta-4
>         Environment: Windows 2000, Tortoise CVS 1.8.26. Maven 2.0.4, release 2.0-beta
>            Reporter: Todd Nine
>         Assigned To: Emmanuel Venisse
> I am receiving errors when attempting to check in on a multiproject release.  Below is
my output.  As you can see, it is not checking in the parent pom.  If I manually execute the
command in the output, the parent pom is correctly checked in.  Is it possible the first file
in the output (which happens to be the parent pom) is not getting added to the arguments when
the commit command is executed?
> [INFO] Checking in modified POMs...
> [INFO] Executing: cvs -z3 -f -d -q commit -R
-F C:\DOCUME~1\u84172\LOCALS~1\Temp\scm-commit-message27749.txt pom.xml messageDrivenSender/pom.xml
messageDrivenPojo/pom.xml messageDrivenDelegate/pom.xml
> [INFO] Working directory: C:\development\ata\utilities
> [INFO] Tagging release with the label utilitiesParent-1_0_0...
> [INFO] Executing: cvs -z3 -f -d -q tag -F -c
> [INFO] Working directory: C:\development\ata\utilities
> [WARNING] Unknown status: '? '.
> [INFO] ---------------------------------------------------------------
> [INFO] ---------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The cvs tag command failed.
> Command output:
> cvs tag: pom.xml is locally modified
> cvs [tag aborted]: correct the above errors first!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message