[
https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319905#comment-319905
]
Anatoly Kupriyanov commented on MRELEASE-777:
---------------------------------------------
The release plugin does a lot strange things which ruin the performance. At the
moment it creates a clone of wc, it build the project twice, it pollutes the wc
with temporary files. Maybe it has a sense for some SCMs, but obviously not for
git.
For git the workflow should be:
1. Check local modifications, fail if any.
2. git clean -xdf
3. Set next version number
4. Commit
5. Create tag
6. mvn deploy
7. Make a snapshot version number
8. Commit
9. Push to git repo
Maybe this is issue to solve in the v3.0. Or maybe for another release plugin.
> release plugin shouldn't git clone if the SCM is git
> ----------------------------------------------------
>
> Key: MRELEASE-777
> URL: https://jira.codehaus.org/browse/MRELEASE-777
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Environment: Linux x86_64, maven 2.2.1
> Reporter: Joel Orlina
> Assignee: Mark Struberg
>
> See here for original issue:
> https://issues.sonatype.org/browse/MVNCENTRAL-202
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
