You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Struberg (JIRA)" <ji...@codehaus.org> on 2011/02/13 16:33:22 UTC

[jira] Commented: (SCM-566) During release the tag is pushed to 'origin' instead of the remote repo specified in developerConnection

    [ http://jira.codehaus.org/browse/SCM-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255854#action_255854 ] 

Mark Struberg commented on SCM-566:
-----------------------------------

Hi!

Which version of the maven-scm-provider-gitexe did you use?
I fixed this as part of SCM-498 in version 1.2.
But it seems I still need to fix the error output of course (still saying 'origin' instead of 'upstream').

> During release the tag is pushed to 'origin' instead of the remote repo specified in developerConnection
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SCM-566
>                 URL: http://jira.codehaus.org/browse/SCM-566
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>            Reporter: Carlo de Wolf
>            Assignee: Mark Struberg
>
> I have origin pointing to http://github.com/wolfc/jboss-ejb3-bom-eap5
> while upstream points to http://github.com/jbossejb3/jboss-ejb3-bom-eap5
> During the release of http://github.com/jbossejb3/jboss-ejb3-bom-eap5/blob/bom-eap5-0.1.3/pom.xml the tag was pushed to origin, not upstream.

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