[
http://jira.codehaus.org/browse/SCM-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Perez updated SCM-475:
------------------------------
Attachment: SCM-475-maven-scm-provider-hg.patch
Hello
Per Sean request - I also had the same requirement -, please find an attached
patch which allow the Mercurial provider to use the pushChanges setting defined
in maven-release-plugin 2.2-SNAPSHOT <configuration>.
Olivier (I hope you're the official maintainer, adressing you because of the
svn logs and because I was sitting close to you at a previous Xebia XKE ;) ), I
have two remarks :
- the diff changes the previous indentation : because this is my 1st patch, I
wanted to follow the rules so I downloaded
http://maven.apache.org/developers/maven-idea-codestyle.xml, and applying this
style did change the indentation (for good) ; so tell me if such a diff is ok,
to me it looks like the indentation is now correct.
- the maven-release-plugin 2.2-SNAPSHOT pom.xml has to be modified to use the
newest maven-scm, as in <scmVersion>1.5-SNAPSHOT</scmVersion>
Cheers :)
Laurent
> hg plugin insists on 'pushing'
> ------------------------------
>
> Key: SCM-475
> URL: http://jira.codehaus.org/browse/SCM-475
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.2
> Reporter: Benson Margulies
> Attachments: SCM-475-maven-scm-provider-hg.patch
>
>
> When I combine the mercurial scm with the release plugin, I'm unhappy to
> discover that the scm insists on doing a push. The whole point of a hg or
> git-based systems is to work in the local clone and push up to the repo at a
> later time. I submit that the plugin should leave the pushing to me, simply
> performing the hg manipulations in the local clone.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
