[
https://issues.apache.org/jira/browse/SCM-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962092#comment-17962092
]
ASF GitHub Bot commented on SCM-566:
------------------------------------
jira-importer commented on issue #779:
URL: https://github.com/apache/maven-scm/issues/779#issuecomment-2964623730
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
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: https://issues.apache.org/jira/browse/SCM-566
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Reporter: Carlo de Wolf
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.5
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
