[
https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338259#comment-338259
]
Paul Millar commented on MRELEASE-812:
--------------------------------------
Hit this problem myself (or one like it). The trigger seems to be an upgrade
of git from 1.8.5.1 to 1.8.5.2, but I'm still double-checking that.
I tried the above work-around posted by Catalin (updating maven-scm version
dependency to 1.8.1) but encountered the problem described in SCM 709: support
for sub-projects/modules is broken.
Is there a way to test SCM 686 and SCM 709 together; e.g., a snapshot or
nightly release of maven-scm I could add as a dependency instead of 1.8.1?
In SCM 709, they cite a lack of feedback as a reason why progress isn't being
made, but it's unclear to me how they expect to receive this feedback if the
patch isn't available for testing somewhere.
> "prepare" does not commit before tagging and therefore deploys snapshot
> instead of release
> ------------------------------------------------------------------------------------------
>
> Key: MRELEASE-812
> URL: https://jira.codehaus.org/browse/MRELEASE-812
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git
> Affects Versions: 2.4
> Reporter: Andrei Pozolotin
> Priority: Critical
> Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt
>
>
> thank you very much for new release!
> http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E
> it seems we need an emergency fix:
> attached are 2 logs:
> 1) mvn-2.3.2.txt invocation that works fine with 2.3.2
> 2) mvn-2.4.0.txt invocation that fails with 2.4
> problem:
> "perform" does not commit tags, deploys snapshot instead of release
> here is project parent:
> http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom
> build is invoked both times with this:
> mvn --define resume=false release:prepare
> mvn --define resume=false release:perform
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
