I didn't explicitly specify a plugin version, so Maven used 2.0. Now i specified 2.1 and it's working.
Manuel On Mon, Jun 6, 2011 at 12:23, Leonard Ehrenfried <[email protected]> wrote: > Which version of the release plugin do you use and in turn which version of > the git scm provider does this pull in? > > I have used version 2.1 of the release plugin with git for a few weeks and > have not noticed any problems with it. > > Lenni > > > On Mon, Jun 6, 2011 at 12:12 PM, Manuel Doninger <[email protected]>wrote: > >> Hi, >> i'm using the Maven release plugin to release a project which is >> stored in a Git repository. Everything works fine until the git tag >> command. The debug Maven output says: >> >> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F >> C:\Windows\TEMP\maven-scm-1039630102.commit >> de.company.statistik.model\pom.xml >> de.company.statistik.batchjob\pom.xml de.company.statistik.web\pom.xml >> pom.xml" [INFO] Working directory: >> N:\Jenkins_Slave\workspace\EDI_Prod_Statistik >> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD" [INFO] Working >> directory: N:\Jenkins_Slave\workspace\EDI_Prod_Statistik [INFO] >> Executing: cmd.exe /X /C "git push >> ssh://user@gitserver:2222/edi/statistik.git production:production" >> [INFO] Working directory: >> N:\Jenkins_Slave\workspace\EDI_Prod_Statistik >> [INFO] Tagging release with the label statistik-0.0.1... [DEBUG] >> ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase >> :: scmTagParameters scmRevision null [INFO] Executing: cmd.exe /X /C >> "git tag -F C:\Windows\TEMP\maven-scm-143343597.commit >> statistik-0.0.1" [INFO] Working directory: N:\Jenkins_Slave\workspace >> mojoFailed org.apache.maven.plugins:maven-release-plugin:2.0(default-cli) >> projectFailed de.markant.edi:statistik:0.0.1-SNAPSHOT [JENKINS] >> Re-archiving N:\Jenkins_Slave\workspace\EDI_Prod_Statistik\pom.xml >> sessionEnded >> >> So as you can see, before the tag command the working directory is >> changed to one level upwards. Consequently git tag fails, because >> there is not the Git repository (that's in >> N:\Jenkins_Slave\workspace\EDI_Prod_Statistik). This execution is from >> our Jenkins instance, but i got the same result if i run the release >> locally. >> Any hints? >> >> Manuel >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
