You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Martin Lichtin <li...@yahoo.com> on 2012/11/13 15:17:33 UTC
mvn release:prepare cannot git-commit the pom.xml change
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
RE: mvn release:prepare cannot git-commit the pom.xml change
Posted by Ken O'Connell <ko...@casenetllc.com>.
I apologize, I replied to the wrong message. Pls disregard.
-----Original Message-----
From: Ken O'Connell [mailto:koconnell@casenetllc.com]
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:rfscholte@apache.org]
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
<li...@yahoo.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn release:prepare cannot git-commit the pom.xml change
Posted by Ken O'Connell <ko...@casenetllc.com>.
Thank you for your replied, but I messaged before that I replied to the wrong thread. (where the subject was similar to this one).
I am not having an issue in regards to correct version of the maven release plugin.
-----Original Message-----
From: Benson Margulies [mailto:bimargulies@gmail.com]
Sent: Tuesday, November 13, 2012 11:45 AM
To: Maven Users List; Ron Wheeler
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
No, pluginManagement. dependencyManagement does not effect plugins.
On Tue, Nov 13, 2012 at 11:06 AM, Ron Wheeler <rw...@artifact-software.com> wrote:
> On 13/11/2012 10:43 AM, Ken O'Connell wrote:
>>
>> 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.
>
> Did you put it in the dependencyManagement section? That controls
> which version the children get to use.
> As a dependency it would only apply to the parent.
>
>
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> 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
>> <li...@yahoo.com>:
>>
>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn release:prepare cannot git-commit the pom.xml change
Posted by Benson Margulies <bi...@gmail.com>.
No, pluginManagement. dependencyManagement does not effect plugins.
On Tue, Nov 13, 2012 at 11:06 AM, Ron Wheeler
<rw...@artifact-software.com> wrote:
> On 13/11/2012 10:43 AM, Ken O'Connell wrote:
>>
>> 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.
>
> Did you put it in the dependencyManagement section? That controls which
> version the children get to use.
> As a dependency it would only apply to the parent.
>
>
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> 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
>> <li...@yahoo.com>:
>>
>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn release:prepare cannot git-commit the pom.xml change
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 13/11/2012 10:43 AM, Ken O'Connell wrote:
> 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.
Did you put it in the dependencyManagement section? That controls which
version the children get to use.
As a dependency it would only apply to the parent.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> 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
> <li...@yahoo.com>:
>
>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn release:prepare cannot git-commit the pom.xml change
Posted by Ken O'Connell <ko...@casenetllc.com>.
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:rfscholte@apache.org]
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
<li...@yahoo.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn release:prepare cannot git-commit the pom.xml change
Posted by Martin Lichtin <li...@yahoo.com>.
I'll try using the git windows port and I guess it will work.
However, could Maven not try to support this environment, understand that it is running in Cygwin and don't use cmd.exe and create a 'normal' tmp path.
----- Original Message -----
> From: "Nord, James" <JN...@nds.com>
> To: Maven Users List <us...@maven.apache.org>; Martin Lichtin <li...@yahoo.com>
> Cc:
> Sent: Tuesday, November 13, 2012 6:25 PM
> Subject: RE: mvn release:prepare cannot git-commit the pom.xml change
>
> Have you tried with the git windows port rather than Cygwin git.
> That works for me on windows with the release plugin.
>
> Mixing windows and DOS paths / tools is never a good combination in my
> experience.
>
> /James
>
> -----Original Message-----
> From: Martin Lichtin [mailto:lichtin@yahoo.com]
> Sent: 13 November 2012 15:50
> To: Maven Users List
> Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
>
> Same with version 2.3.2 (many thanks of course for pointing out the old version
> I was trying with).
>
> [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-915771020.commit pom.xml"
> [INFO] Working directory:
> C:\users\mli\nuc\core\master\main\inuc
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10.227s
> [INFO] Finished at: Tue Nov 13 16:45:35 CET 2012 [INFO] Final Memory: 6M/102M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.3.2: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-915771020.commit': No such
> file or directory
>
> Strangely enough, it looks like a Git issue?
>
> $ echo X > "C:\cygwin\tmp\commit"
> $ cat "C:\cygwin\tmp\commit"
> X
> $ cmd.exe /X /C "git commit --verbose -F C:\cygwin\tmp\commit
> pom.xml"
> fatal: could not read log file 'inuc/C:\cygwin\tmp\commit':
> No such file or directory
>
>
> $ git --version
> git version 1.7.9
>
>
>
>
>> ________________________________
>> From: Robert Scholte <rf...@apache.org>
>> To: Maven Users List <us...@maven.apache.org>
>> Sent: Tuesday, November 13, 2012 3:55 PM
>> 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
> <li...@yahoo.com>:
>>
>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
> ________________________________
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have
> received this message in error, please immediately notify the postmaster@nds.com
> and delete it from your system as well as any copies. The content of e-mails as
> well as traffic data may be monitored by NDS for employment and security
> purposes. To protect the environment please do not print this e-mail unless
> necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX,
> United Kingdom. A company registered in England and Wales. Registered no.
> 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn release:prepare cannot git-commit the pom.xml change
Posted by "Nord, James" <JN...@nds.com>.
Have you tried with the git windows port rather than Cygwin git.
That works for me on windows with the release plugin.
Mixing windows and DOS paths / tools is never a good combination in my experience.
/James
-----Original Message-----
From: Martin Lichtin [mailto:lichtin@yahoo.com]
Sent: 13 November 2012 15:50
To: Maven Users List
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
Same with version 2.3.2 (many thanks of course for pointing out the old version I was trying with).
[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-915771020.commit pom.xml"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.227s
[INFO] Finished at: Tue Nov 13 16:45:35 CET 2012 [INFO] Final Memory: 6M/102M [INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2: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-915771020.commit': No such file or directory
Strangely enough, it looks like a Git issue?
$ echo X > "C:\cygwin\tmp\commit"
$ cat "C:\cygwin\tmp\commit"
X
$ cmd.exe /X /C "git commit --verbose -F C:\cygwin\tmp\commit pom.xml"
fatal: could not read log file 'inuc/C:\cygwin\tmp\commit': No such file or directory
$ git --version
git version 1.7.9
>________________________________
> From: Robert Scholte <rf...@apache.org>
>To: Maven Users List <us...@maven.apache.org>
>Sent: Tuesday, November 13, 2012 3:55 PM
>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 <li...@yahoo.com>:
>
>> 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: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
________________________________
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn release:prepare cannot git-commit the pom.xml change
Posted by Martin Lichtin <li...@yahoo.com>.
Same with version 2.3.2 (many thanks of course for pointing out the old version I was trying with).
[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-915771020.commit pom.xml"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.227s
[INFO] Finished at: Tue Nov 13 16:45:35 CET 2012
[INFO] Final Memory: 6M/102M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2: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-915771020.commit': No such file or directory
Strangely enough, it looks like a Git issue?
$ echo X > "C:\cygwin\tmp\commit"
$ cat "C:\cygwin\tmp\commit"
X
$ cmd.exe /X /C "git commit --verbose -F C:\cygwin\tmp\commit pom.xml"
fatal: could not read log file 'inuc/C:\cygwin\tmp\commit': No such file or directory
$ git --version
git version 1.7.9
>________________________________
> From: Robert Scholte <rf...@apache.org>
>To: Maven Users List <us...@maven.apache.org>
>Sent: Tuesday, November 13, 2012 3:55 PM
>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 <li...@yahoo.com>:
>
>> 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: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
Re: mvn release:prepare cannot git-commit the pom.xml change
Posted by Robert Scholte <rf...@apache.org>.
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
<li...@yahoo.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org