[
https://jira.codehaus.org/browse/MRELEASE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bradley Baetz reopened MRELEASE-885:
------------------------------------
This is still broken, using v2.5.1 (and v1.9.2 of the scm plugin) The push
works, but the tag fails because the path is wrong:
...
[INFO] Executing: /bin/sh -c cd /tmp/maven-release-bug/build && git commit
--verbose -F /tmp/maven-scm-586872819.commit pom.xml
/tmp/maven-release-bug/core/pom.xml
[INFO] Working directory: /tmp/maven-release-bug/build
[INFO] Executing: /bin/sh -c cd /tmp/maven-release-bug/build && git
symbolic-ref HEAD
[INFO] Working directory: /tmp/maven-release-bug/build
[INFO] Executing: /bin/sh -c cd /tmp/maven-release-bug/build && git push
[email protected]:bbaetz/maven-release-bug.git refs/heads/master:refs/heads/master
[INFO] Working directory: /tmp/maven-release-bug/build
[INFO] Tagging release with the label project-1.0.0...
[DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
[DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
[DEBUG] ScmTagPhase :: fileSet basedir = /tmp/maven-release-bug; files = []
[INFO] Executing: /bin/sh -c cd /tmp/maven-release-bug && git tag -F
/tmp/maven-scm-1258073395.commit project-1.0.0
[INFO] Working directory: /tmp/maven-release-bug
[INFO] Executing: /bin/sh -c cd /tmp/maven-release-bug && git push
[email protected]:bbaetz refs/tags/project-1.0.0
[INFO] Working directory: /tmp/maven-release-bug
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] project ........................................... FAILURE [9.952s]
[INFO] project-core ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.141s
[INFO] Finished at: Mon Sep 29 14:15:12 EST 2014
[INFO] Final Memory: 9M/113M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on
project project: Unable to tag SCM
[ERROR] Provider message:
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] ERROR: Repository not found.
[ERROR] fatal: Could not read from remote repository.
[ERROR]
[ERROR] Please make sure you have the correct access rights
[ERROR] and the repository exists.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on
project project: Unable to tag SCM
Provider message:
The git-push command failed.
Command output:
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM
> When the base pom is a subdirectory, tagging fails in GIT
> ---------------------------------------------------------
>
> Key: MRELEASE-885
> URL: https://jira.codehaus.org/browse/MRELEASE-885
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git, scm
> Affects Versions: 2.3.2, 2.5
> Environment: linux (fedora 20)
> Reporter: Bradley Baetz
> Assignee: Benson Margulies
> Fix For: 2.5.1
>
>
> (NOTE, this is not the same as MRELEASE-875. I think)
> Given a GIT checkout with a project structure of:
> project/
> dir1/pom.xml
> dir2/pom.xml
> Given an <scm> config of:
> <developerConnection>scm:git:ssh://[email protected]:bbaetz/maven-release-bug.git</developerConnection>
> the maven-release plugin correctly commits the pom file, but fails to tag.
> The problem is that its stripping off one level of the URL, and doing:
> [INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project && git push
> ssh://[email protected]:bbaetz refs/tags/project-1.0.0
> which is wrong for git
> To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the
> scm settings to your own, and run:
> mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT
> -DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform
> I've tried various combinations of maven-release-plugin and maven-scm-plugin
> versions, with no luck
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
