I apologize, I replied to the wrong message. Pls disregard.

-----Original Message-----
From: Ken O'Connell [mailto:[email protected]]
Sent: Tuesday, November 13, 2012 10:44 AM
To: Maven Users List
Subject: RE: mvn release:prepare cannot git-commit the pom.xml change

I put this version in my parent pom after you first suggested it, but it seems 
like it not using that version, as you pointed out.

-----Original Message-----
From: Robert Scholte [mailto:[email protected]]
Sent: Tuesday, November 13, 2012 9:56 AM
To: Maven Users List
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change

The logging says:
"org.apache.maven.plugins:maven-release-plugin:2.0:prepare"
This means you're using a pretty old version of the maven-release-plugin.
Try to lock the version on 2.3.2 first.

Robert


Op Tue, 13 Nov 2012 15:17:33 +0100 schreef Martin Lichtin
<[email protected]>:

> Hi
> As a first-time user of the "release" plugin, I'm running into the
> following problem:
>
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
> [INFO] Executing: cmd.exe /X /C "git status"
> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\cygwin\tmp\maven-scm-1106545469.commit pom.xml"
> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 6.521s
> [INFO] Finished at: Tue Nov 13 14:44:27 CET 2012 [INFO] Final Memory:
> 7M/104M [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.0:prepare
> (default-cli) on project inuc: Unable to commit files [ERROR] Provider
> message:
> [ERROR] The git-commit command failed.
> [ERROR] Command output:
> [ERROR] fatal: could not read log file
> 'inuc/C:\cygwin\tmp\maven-scm-1106545469.commit': No such file or
> directory
>
> Note how the last line shows a log file name erroneously prefixed with
> the module name.
> Is this a problem caused by cmd.exe versus cygwin interaction? Or
> could it even be a git bug.
>
> Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


CONFIDENTIALITY NOTICE:  This e-mail and the information transmitted within 
including any attachments is only for the recipient(s) to which it is intended 
and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of; or taking of any action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please send the e-mail 
back by replying to the sender and permanently delete the entire message and 
its attachments from all computers and network systems involved in its receipt.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


CONFIDENTIALITY NOTICE:  This e-mail and the information transmitted within 
including any attachments is only for the recipient(s) to which it is intended 
and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of; or taking of any action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please send the e-mail 
back by replying to the sender and permanently delete the entire message and 
its attachments from all computers and network systems involved in its receipt.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to