Daniel Burrell created MRELEASE-1030:
----------------------------------------

             Summary: Introduce flag to push once, not twice, during 
release:prepare
                 Key: MRELEASE-1030
                 URL: https://issues.apache.org/jira/browse/MRELEASE-1030
             Project: Maven Release Plugin
          Issue Type: Improvement
          Components: prepare
    Affects Versions: 2.5.3
            Reporter: Daniel Burrell


When performing release:prepare the following action is taken.
 * solidify releases
 * commit and push 
 * tag this commit
 * push
 * move to next snapshot
 * commit and push

 

This behaviour in a git based CI environment results in additional unnecessary 
builds as an I tagged commit is delivered, quickly followed by the same commit 
in tagged form.

The commit and push that happens in stage 2 above should be commit only.

the push should be a push of the tag (which implicitly pushes the commit).

To maintain backward compatibility this should be a flag.

I have not read the source code but I suspect this issues is caused by generic 
usage of / delegation to the scm plugin, without consideration of the nuances 
of git. The scm plugin does indeed have a flag for this purpose but we are not 
making use of it or exposing it at the release plugin level

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to