You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fabrizio Giudici (JIRA)" <ji...@codehaus.org> on 2013/05/16 23:29:52 UTC

[jira] (SCM-720) Add a 'push' goal

Fabrizio Giudici created SCM-720:
------------------------------------

             Summary: Add a 'push' goal
                 Key: SCM-720
                 URL: https://jira.codehaus.org/browse/SCM-720
             Project: Maven SCM
          Issue Type: Bug
            Reporter: Fabrizio Giudici


I've been using for a couple of years a Maven release process where artifacts are first deployed to a local directory and Mercurial/Git changes are not pushed. This makes it possible to roll back all the changes in case of testing, when either the remote SCM repo or Maven repo are not reachable for a transient network error, etc., as well as just retry pushing/deploying the artifacts without re-running the whole release cycle.

Final pushing and deploying are performed by re-running Maven with a specified profile. I'm able to perform hg/git push by invoking their executables with the proper parameters by means of the antrun-plugin, but it's cumbersome. It would be so much better to just invoke scm:push.

Of course I'm aware that this needs implementation through all the providers. For distributed SCMs, push must be a full push (e.g. Git should push also tags); for non distributed SCMs, such as Subversion, the goals should just do nothing.

--
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