maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-777) release plugin shouldn't git clone if the SCM is git
Date Fri, 05 Oct 2012 21:31:36 GMT

     [ https://jira.codehaus.org/browse/MRELEASE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Struberg closed MRELEASE-777.
----------------------------------

    Resolution: Not A Bug

There are config options for this exact scenario

<localCheckout>true</localCheckout>
<pushChanges>false</pushChanges

Please add those 2 to the <configuration> section of the maven-release-plugin.

Here is the explanation why:
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
                
> 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

        

Mime
View raw message