You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andrew Pennebaker <an...@gmail.com> on 2015/04/10 17:36:31 UTC
ScmTagPhase cd'ing to wrong directory
When I try to mvn release:prepare my git project, it fails on the
ScmTagPhase step, because it tries to git push --tags from ~/Desktop/src/
rather as the working directory, rather than the Maven project directory I
started in, ~/Desktop/src/doppler-ws/.
Why might this happen?
--
Cheers,
Andrew Pennebaker
www.yellosoft.us
Re: ScmTagPhase cd'ing to wrong directory
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Andrew,
can you show us your pom file? Or may be you are working on a github
project so a link will work as well...
On 4/10/15 5:36 PM, Andrew Pennebaker wrote:
> When I try to mvn release:prepare my git project, it fails on the
> ScmTagPhase step, because it tries to git push --tags from ~/Desktop/src/
> rather as the working directory, rather than the Maven project directory I
> started in, ~/Desktop/src/doppler-ws/.
>
> Why might this happen?
>
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ScmTagPhase cd'ing to wrong directory
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Andrew,
On 4/10/15 6:54 PM, Andrew Pennebaker wrote:
> Thanks, I'll try updating to maven-release-plugin 2.5.x.
>
> Believe it or not, some of our projects are using Maven
> plugins/configurations that have not yet been updated for Maven 3
> compatibility :P
I believe this...but be aware of this:
http://mail-archives.apache.org/mod_mbox/maven-announce/201503.mbox/%3C20150320213920.6AE4B17423%40minotaur.apache.org%3E
Kind regards
Karl Heinz Marbaise
>
> On Fri, Apr 10, 2015 at 11:45 AM, Karl Heinz Marbaise <khmarbaise@gmx.de
> <ma...@gmx.de>> wrote:
>
> Hi Andrew,
>
> check if updating the release plugin to newest version could fix the
> problem...
> Currently 2.5.1 is uptodate...
>
> Apart from that really a good reason to use Maven 2.X instead of
> newer versions?
>
> Kind regards
> Karl Heinz Marbaise
>
> On 4/10/15 6:41 PM, Andrew Pennebaker wrote:
>
> Error trace:
>
> doppler-ws (master) $ mvn release:clean
> doppler-ws (master) $ mvn -e -X -Darguments='-DskipTests'
> release:perform
> -P staging
>
> ...
>
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd
> /Users/apennebaker/Desktop/__src/doppler-ws
> && git add -- doppler-api/pom.xml pom.xml doppler-client/pom.xml
> doppler-hive/doppler-hive-__functions/pom.xml
> doppler-hive/doppler-hive-__workflows/pom.xml doppler-hive/pom.xml
> doppler-impl/pom.xml
> [INFO] Working directory:
> /Users/apennebaker/Desktop/__src/doppler-ws
> [INFO] Executing: /bin/sh -c cd
> /Users/apennebaker/Desktop/__src/doppler-ws
> && git status
> [INFO] Working directory:
> /Users/apennebaker/Desktop/__src/doppler-ws
> [DEBUG] On branch master
> [DEBUG] Your branch is up-to-date with 'origin/master'.
> [DEBUG] Changes to be committed:
> [DEBUG] (use "git reset HEAD <file>..." to unstage)
> [DEBUG]
> [DEBUG] modified: doppler-api/pom.xml
> [DEBUG] modified: doppler-client/pom.xml
> [DEBUG] modified:
> doppler-hive/doppler-hive-__functions/pom.xml
> [DEBUG] modified:
> doppler-hive/doppler-hive-__workflows/pom.xml
> [DEBUG] modified: doppler-hive/pom.xml
> [DEBUG] modified: doppler-impl/pom.xml
> [DEBUG] modified: pom.xml
> [DEBUG]
> [INFO] Executing: /bin/sh -c cd
> /Users/apennebaker/Desktop/__src/doppler-ws
> && git commit --verbose -F
> /var/folders/_9/__shv02r4n1nx9ksvx6w___nd4pw0000gp/T/maven-scm-__1887582615.commit
> doppler-api/pom.xml pom.xml doppler-client/pom.xml
> doppler-hive/doppler-hive-__functions/pom.xml
> doppler-hive/doppler-hive-__workflows/pom.xml doppler-hive/pom.xml
> doppler-impl/pom.xml
> [INFO] Working directory:
> /Users/apennebaker/Desktop/__src/doppler-ws
> [INFO] Executing: /bin/sh -c cd
> /Users/apennebaker/Desktop/__src/doppler-ws
> && git symbolic-ref HEAD
> [INFO] Working directory:
> /Users/apennebaker/Desktop/__src/doppler-ws
> [INFO] Executing: /bin/sh -c cd
> /Users/apennebaker/Desktop/__src/doppler-ws
> && git push
> git@gitlab.colo.__networkedinsights.com:product-__engineering/doppler-ws.git
> master:master
> [INFO] Working directory:
> /Users/apennebaker/Desktop/__src/doppler-ws
> [INFO] Tagging release with the label doppler-1.7.0...
> [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
> [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src
> && git tag
> -F
> /var/folders/_9/__shv02r4n1nx9ksvx6w___nd4pw0000gp/T/maven-scm-__450374444.commit
> doppler-1.7.0
> [INFO] Working directory: /Users/apennebaker/Desktop/src
> [INFO]
> ------------------------------__------------------------------__------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------__------------------------------__------------
> [INFO] Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> [INFO]
> ------------------------------__------------------------------__------------
> [DEBUG] Trace
> org.apache.maven.__BuildFailureException: Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeGoals(__DefaultLifecycleExecutor.java:__715)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeStandaloneGoal(__DefaultLifecycleExecutor.java:__569)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeGoal(__DefaultLifecycleExecutor.java:__539)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeGoalAndHandleFailures(__DefaultLifecycleExecutor.java:__387)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeTaskSegments(__DefaultLifecycleExecutor.java:__284)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__execute(__DefaultLifecycleExecutor.java:__180)
> at
> org.apache.maven.DefaultMaven.__doExecute(DefaultMaven.java:__328)
> at
> org.apache.maven.DefaultMaven.__execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.__main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.__CompatibleMain.main(__CompatibleMain.java:60)
> at sun.reflect.__NativeMethodAccessorImpl.__invoke0(Native
> Method)
> at
> sun.reflect.__NativeMethodAccessorImpl.__invoke(__NativeMethodAccessorImpl.java:__57)
> at
> sun.reflect.__DelegatingMethodAccessorImpl.__invoke(__DelegatingMethodAccessorImpl.__java:43)
> at java.lang.reflect.Method.__invoke(Method.java:606)
> 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.__MojoFailureException:
> Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.plugins.__release.PrepareReleaseMojo.__prepareRelease(__PrepareReleaseMojo.java:219)
> at
> org.apache.maven.plugins.__release.PrepareReleaseMojo.__execute(PrepareReleaseMojo.__java:181)
> at
> org.apache.maven.plugin.__DefaultPluginManager.__executeMojo(__DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.__DefaultLifecycleExecutor.__executeGoals(__DefaultLifecycleExecutor.java:__694)
> ... 17 more
> Caused by:
> org.apache.maven.shared.__release.scm.__ReleaseScmCommandException:
> Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.shared.__release.phase.ScmTagPhase.__execute(ScmTagPhase.java:118)
> at
> org.apache.maven.shared.__release.DefaultReleaseManager.__prepare(DefaultReleaseManager.__java:203)
> at
> org.apache.maven.shared.__release.DefaultReleaseManager.__prepare(DefaultReleaseManager.__java:140)
> at
> org.apache.maven.shared.__release.DefaultReleaseManager.__prepare(DefaultReleaseManager.__java:103)
> at
> org.apache.maven.plugins.__release.PrepareReleaseMojo.__prepareRelease(__PrepareReleaseMojo.java:211)
> ... 20 more
> [INFO]
> ------------------------------__------------------------------__------------
> [INFO] Total time: 1 minute 30 seconds
> [INFO] Finished at: Fri Apr 10 10:50:19 CDT 2015
> [INFO] Final Memory: 19M/439M
> [INFO]
> ------------------------------__------------------------------__------------
>
> To be sure, my git/SSH keys are in fact correctly configured,
> including the
> file permissions. I can successfully run git commands manually,
> it's only
> the maven-release-plugin that's doing things wrong for some reason.
>
> System:
>
> * maven-release-plugin 2.4
> * Maven 2.2.1
> * Java JDK 1.7
> * git 2.3.1
> * Mac OS X 10.10.2 Yosemite
>
> On Fri, Apr 10, 2015 at 10:40 AM, Dishant Anand <
> dishant.anand@techblue.co.uk
> <ma...@techblue.co.uk>> wrote:
>
> The reason it would be failing because at the it may have
> tried to commit
> files for you onto the git and to do that it uses your ssh
> connection ,
> which is authenticated via a ssh key stored in your .ssh
> folder ,
> I am sure you are missing that key which resulted in this
> failure.
>
> Please make sure your .ssh folder contain the appropriate keys ,
>
> Cheers,
> Dishant Anand
> On 10/04/2015 16:36, Andrew Pennebaker wrote:
>
> When I try to mvn release:prepare my git project, it
> fails on the
> ScmTagPhase step, because it tries to git push --tags
> from ~/Desktop/src/
> rather as the working directory, rather than the Maven
> project directory I
> started in, ~/Desktop/src/doppler-ws/.
>
> Why might this happen?
>
>
> ------------------------------__------------------------------__---------
> To unsubscribe, e-mail: users-unsubscribe@maven.__apache.org
> <ma...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
> <ma...@maven.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ScmTagPhase cd'ing to wrong directory
Posted by Andrew Pennebaker <an...@gmail.com>.
Thanks, I'll try updating to maven-release-plugin 2.5.x.
Believe it or not, some of our projects are using Maven
plugins/configurations that have not yet been updated for Maven 3
compatibility :P
On Fri, Apr 10, 2015 at 11:45 AM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi Andrew,
>
> check if updating the release plugin to newest version could fix the
> problem...
> Currently 2.5.1 is uptodate...
>
> Apart from that really a good reason to use Maven 2.X instead of newer
> versions?
>
> Kind regards
> Karl Heinz Marbaise
>
> On 4/10/15 6:41 PM, Andrew Pennebaker wrote:
>
>> Error trace:
>>
>> doppler-ws (master) $ mvn release:clean
>> doppler-ws (master) $ mvn -e -X -Darguments='-DskipTests' release:perform
>> -P staging
>>
>> ...
>>
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
>> && git add -- doppler-api/pom.xml pom.xml doppler-client/pom.xml
>> doppler-hive/doppler-hive-functions/pom.xml
>> doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
>> doppler-impl/pom.xml
>> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
>> && git status
>> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
>> [DEBUG] On branch master
>> [DEBUG] Your branch is up-to-date with 'origin/master'.
>> [DEBUG] Changes to be committed:
>> [DEBUG] (use "git reset HEAD <file>..." to unstage)
>> [DEBUG]
>> [DEBUG] modified: doppler-api/pom.xml
>> [DEBUG] modified: doppler-client/pom.xml
>> [DEBUG] modified: doppler-hive/doppler-hive-functions/pom.xml
>> [DEBUG] modified: doppler-hive/doppler-hive-workflows/pom.xml
>> [DEBUG] modified: doppler-hive/pom.xml
>> [DEBUG] modified: doppler-impl/pom.xml
>> [DEBUG] modified: pom.xml
>> [DEBUG]
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
>> && git commit --verbose -F
>> /var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-
>> 1887582615.commit
>> doppler-api/pom.xml pom.xml doppler-client/pom.xml
>> doppler-hive/doppler-hive-functions/pom.xml
>> doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
>> doppler-impl/pom.xml
>> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
>> && git symbolic-ref HEAD
>> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
>> && git push git@gitlab.colo.networkedinsights.com:product-
>> engineering/doppler-ws.git
>> master:master
>> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
>> [INFO] Tagging release with the label doppler-1.7.0...
>> [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
>> [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
>> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src && git tag
>> -F
>> /var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-
>> 450374444.commit
>> doppler-1.7.0
>> [INFO] Working directory: /Users/apennebaker/Desktop/src
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to tag SCM
>> Provider message:
>> The git-tag command failed.
>> Command output:
>> fatal: Not a git repository (or any of the parent directories): .git
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [DEBUG] Trace
>> org.apache.maven.BuildFailureException: Unable to tag SCM
>> Provider message:
>> The git-tag command failed.
>> Command output:
>> fatal: Not a git repository (or any of the parent directories): .git
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> DefaultLifecycleExecutor.java:715)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.
>> executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>> DefaultLifecycleExecutor.java:539)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.
>> executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>> DefaultLifecycleExecutor.java:284)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>> DefaultLifecycleExecutor.java:180)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> 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.MojoFailureException: Unable to tag
>> SCM
>> Provider message:
>> The git-tag command failed.
>> Command output:
>> fatal: Not a git repository (or any of the parent directories): .git
>>
>> at
>> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(
>> PrepareReleaseMojo.java:219)
>> at
>> org.apache.maven.plugins.release.PrepareReleaseMojo.
>> execute(PrepareReleaseMojo.java:181)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>> DefaultPluginManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> DefaultLifecycleExecutor.java:694)
>> ... 17 more
>> Caused by: org.apache.maven.shared.release.scm.
>> ReleaseScmCommandException:
>> Unable to tag SCM
>> Provider message:
>> The git-tag command failed.
>> Command output:
>> fatal: Not a git repository (or any of the parent directories): .git
>>
>> at
>> org.apache.maven.shared.release.phase.ScmTagPhase.
>> execute(ScmTagPhase.java:118)
>> at
>> org.apache.maven.shared.release.DefaultReleaseManager.
>> prepare(DefaultReleaseManager.java:203)
>> at
>> org.apache.maven.shared.release.DefaultReleaseManager.
>> prepare(DefaultReleaseManager.java:140)
>> at
>> org.apache.maven.shared.release.DefaultReleaseManager.
>> prepare(DefaultReleaseManager.java:103)
>> at
>> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(
>> PrepareReleaseMojo.java:211)
>> ... 20 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 1 minute 30 seconds
>> [INFO] Finished at: Fri Apr 10 10:50:19 CDT 2015
>> [INFO] Final Memory: 19M/439M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> To be sure, my git/SSH keys are in fact correctly configured, including
>> the
>> file permissions. I can successfully run git commands manually, it's only
>> the maven-release-plugin that's doing things wrong for some reason.
>>
>> System:
>>
>> * maven-release-plugin 2.4
>> * Maven 2.2.1
>> * Java JDK 1.7
>> * git 2.3.1
>> * Mac OS X 10.10.2 Yosemite
>>
>> On Fri, Apr 10, 2015 at 10:40 AM, Dishant Anand <
>> dishant.anand@techblue.co.uk> wrote:
>>
>> The reason it would be failing because at the it may have tried to commit
>>> files for you onto the git and to do that it uses your ssh connection ,
>>> which is authenticated via a ssh key stored in your .ssh folder ,
>>> I am sure you are missing that key which resulted in this failure.
>>>
>>> Please make sure your .ssh folder contain the appropriate keys ,
>>>
>>> Cheers,
>>> Dishant Anand
>>> On 10/04/2015 16:36, Andrew Pennebaker wrote:
>>>
>>> When I try to mvn release:prepare my git project, it fails on the
>>>> ScmTagPhase step, because it tries to git push --tags from
>>>> ~/Desktop/src/
>>>> rather as the working directory, rather than the Maven project
>>>> directory I
>>>> started in, ~/Desktop/src/doppler-ws/.
>>>>
>>>> Why might this happen?
>>>>
>>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Cheers,
Andrew Pennebaker
www.yellosoft.us
Re: ScmTagPhase cd'ing to wrong directory
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Andrew,
check if updating the release plugin to newest version could fix the
problem...
Currently 2.5.1 is uptodate...
Apart from that really a good reason to use Maven 2.X instead of newer
versions?
Kind regards
Karl Heinz Marbaise
On 4/10/15 6:41 PM, Andrew Pennebaker wrote:
> Error trace:
>
> doppler-ws (master) $ mvn release:clean
> doppler-ws (master) $ mvn -e -X -Darguments='-DskipTests' release:perform
> -P staging
>
> ...
>
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
> && git add -- doppler-api/pom.xml pom.xml doppler-client/pom.xml
> doppler-hive/doppler-hive-functions/pom.xml
> doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
> doppler-impl/pom.xml
> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
> && git status
> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
> [DEBUG] On branch master
> [DEBUG] Your branch is up-to-date with 'origin/master'.
> [DEBUG] Changes to be committed:
> [DEBUG] (use "git reset HEAD <file>..." to unstage)
> [DEBUG]
> [DEBUG] modified: doppler-api/pom.xml
> [DEBUG] modified: doppler-client/pom.xml
> [DEBUG] modified: doppler-hive/doppler-hive-functions/pom.xml
> [DEBUG] modified: doppler-hive/doppler-hive-workflows/pom.xml
> [DEBUG] modified: doppler-hive/pom.xml
> [DEBUG] modified: doppler-impl/pom.xml
> [DEBUG] modified: pom.xml
> [DEBUG]
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
> && git commit --verbose -F
> /var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-1887582615.commit
> doppler-api/pom.xml pom.xml doppler-client/pom.xml
> doppler-hive/doppler-hive-functions/pom.xml
> doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
> doppler-impl/pom.xml
> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
> && git symbolic-ref HEAD
> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
> && git push git@gitlab.colo.networkedinsights.com:product-engineering/doppler-ws.git
> master:master
> [INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
> [INFO] Tagging release with the label doppler-1.7.0...
> [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
> [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
> [INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src && git tag
> -F
> /var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-450374444.commit
> doppler-1.7.0
> [INFO] Working directory: /Users/apennebaker/Desktop/src
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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.MojoFailureException: Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to tag SCM
> Provider message:
> The git-tag command failed.
> Command output:
> fatal: Not a git repository (or any of the parent directories): .git
>
> at
> org.apache.maven.shared.release.phase.ScmTagPhase.execute(ScmTagPhase.java:118)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
> ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1 minute 30 seconds
> [INFO] Finished at: Fri Apr 10 10:50:19 CDT 2015
> [INFO] Final Memory: 19M/439M
> [INFO]
> ------------------------------------------------------------------------
>
> To be sure, my git/SSH keys are in fact correctly configured, including the
> file permissions. I can successfully run git commands manually, it's only
> the maven-release-plugin that's doing things wrong for some reason.
>
> System:
>
> * maven-release-plugin 2.4
> * Maven 2.2.1
> * Java JDK 1.7
> * git 2.3.1
> * Mac OS X 10.10.2 Yosemite
>
> On Fri, Apr 10, 2015 at 10:40 AM, Dishant Anand <
> dishant.anand@techblue.co.uk> wrote:
>
>> The reason it would be failing because at the it may have tried to commit
>> files for you onto the git and to do that it uses your ssh connection ,
>> which is authenticated via a ssh key stored in your .ssh folder ,
>> I am sure you are missing that key which resulted in this failure.
>>
>> Please make sure your .ssh folder contain the appropriate keys ,
>>
>> Cheers,
>> Dishant Anand
>> On 10/04/2015 16:36, Andrew Pennebaker wrote:
>>
>>> When I try to mvn release:prepare my git project, it fails on the
>>> ScmTagPhase step, because it tries to git push --tags from ~/Desktop/src/
>>> rather as the working directory, rather than the Maven project directory I
>>> started in, ~/Desktop/src/doppler-ws/.
>>>
>>> Why might this happen?
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ScmTagPhase cd'ing to wrong directory
Posted by Andrew Pennebaker <an...@gmail.com>.
Error trace:
doppler-ws (master) $ mvn release:clean
doppler-ws (master) $ mvn -e -X -Darguments='-DskipTests' release:perform
-P staging
...
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
&& git add -- doppler-api/pom.xml pom.xml doppler-client/pom.xml
doppler-hive/doppler-hive-functions/pom.xml
doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
doppler-impl/pom.xml
[INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
&& git status
[INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
[DEBUG] On branch master
[DEBUG] Your branch is up-to-date with 'origin/master'.
[DEBUG] Changes to be committed:
[DEBUG] (use "git reset HEAD <file>..." to unstage)
[DEBUG]
[DEBUG] modified: doppler-api/pom.xml
[DEBUG] modified: doppler-client/pom.xml
[DEBUG] modified: doppler-hive/doppler-hive-functions/pom.xml
[DEBUG] modified: doppler-hive/doppler-hive-workflows/pom.xml
[DEBUG] modified: doppler-hive/pom.xml
[DEBUG] modified: doppler-impl/pom.xml
[DEBUG] modified: pom.xml
[DEBUG]
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
&& git commit --verbose -F
/var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-1887582615.commit
doppler-api/pom.xml pom.xml doppler-client/pom.xml
doppler-hive/doppler-hive-functions/pom.xml
doppler-hive/doppler-hive-workflows/pom.xml doppler-hive/pom.xml
doppler-impl/pom.xml
[INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
&& git symbolic-ref HEAD
[INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src/doppler-ws
&& git push git@gitlab.colo.networkedinsights.com:product-engineering/doppler-ws.git
master:master
[INFO] Working directory: /Users/apennebaker/Desktop/src/doppler-ws
[INFO] Tagging release with the label doppler-1.7.0...
[DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
[DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
[INFO] Executing: /bin/sh -c cd /Users/apennebaker/Desktop/src && git tag
-F
/var/folders/_9/shv02r4n1nx9ksvx6w_nd4pw0000gp/T/maven-scm-450374444.commit
doppler-1.7.0
[INFO] Working directory: /Users/apennebaker/Desktop/src
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The git-tag command failed.
Command output:
fatal: Not a git repository (or any of the parent directories): .git
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to tag SCM
Provider message:
The git-tag command failed.
Command output:
fatal: Not a git repository (or any of the parent directories): .git
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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.MojoFailureException: Unable to tag SCM
Provider message:
The git-tag command failed.
Command output:
fatal: Not a git repository (or any of the parent directories): .git
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
Unable to tag SCM
Provider message:
The git-tag command failed.
Command output:
fatal: Not a git repository (or any of the parent directories): .git
at
org.apache.maven.shared.release.phase.ScmTagPhase.execute(ScmTagPhase.java:118)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
... 20 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 minute 30 seconds
[INFO] Finished at: Fri Apr 10 10:50:19 CDT 2015
[INFO] Final Memory: 19M/439M
[INFO]
------------------------------------------------------------------------
To be sure, my git/SSH keys are in fact correctly configured, including the
file permissions. I can successfully run git commands manually, it's only
the maven-release-plugin that's doing things wrong for some reason.
System:
* maven-release-plugin 2.4
* Maven 2.2.1
* Java JDK 1.7
* git 2.3.1
* Mac OS X 10.10.2 Yosemite
On Fri, Apr 10, 2015 at 10:40 AM, Dishant Anand <
dishant.anand@techblue.co.uk> wrote:
> The reason it would be failing because at the it may have tried to commit
> files for you onto the git and to do that it uses your ssh connection ,
> which is authenticated via a ssh key stored in your .ssh folder ,
> I am sure you are missing that key which resulted in this failure.
>
> Please make sure your .ssh folder contain the appropriate keys ,
>
> Cheers,
> Dishant Anand
> On 10/04/2015 16:36, Andrew Pennebaker wrote:
>
>> When I try to mvn release:prepare my git project, it fails on the
>> ScmTagPhase step, because it tries to git push --tags from ~/Desktop/src/
>> rather as the working directory, rather than the Maven project directory I
>> started in, ~/Desktop/src/doppler-ws/.
>>
>> Why might this happen?
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Cheers,
Andrew Pennebaker
www.yellosoft.us
Re: ScmTagPhase cd'ing to wrong directory
Posted by Dishant Anand <di...@techblue.co.uk>.
The reason it would be failing because at the it may have tried to
commit files for you onto the git and to do that it uses your ssh
connection , which is authenticated via a ssh key stored in your .ssh
folder ,
I am sure you are missing that key which resulted in this failure.
Please make sure your .ssh folder contain the appropriate keys ,
Cheers,
Dishant Anand
On 10/04/2015 16:36, Andrew Pennebaker wrote:
> When I try to mvn release:prepare my git project, it fails on the
> ScmTagPhase step, because it tries to git push --tags from ~/Desktop/src/
> rather as the working directory, rather than the Maven project directory I
> started in, ~/Desktop/src/doppler-ws/.
>
> Why might this happen?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org