[ 
https://issues.apache.org/jira/browse/SCM-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962772#comment-17962772
 ] 

ASF GitHub Bot commented on SCM-730:
------------------------------------

jira-importer opened a new issue, #938:
URL: https://github.com/apache/maven-scm/issues/938

   **[Raúl 
Wegmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rwegmann)**
 opened 
**[SCM-730](https://issues.apache.org/jira/browse/SCM-730?redirect=false)** and 
commented
   
   Similar to SCM-696, SVN branching (e.g. when executing `mvn release:branch`) 
is failing when using a svn+ssh://username@host style URL.
   
   See 
https://github.com/rwegmann/maven-scm/commit/1193d2946a9a357462e5465c83c56b3a545e257d
 with the one-line patch.
   
   There may be other instances where the URL might require "fixing", but I 
sadly do not have time to look into it.
   
   
   ---
   
   **Affects:** 1.8.1
   
   **Issue Links:**
   - [SCM-734](https://issues.apache.org/jira/browse/SCM-734) SVN branching 
fails with svn+ssh://username@host URL
    (_**"duplicates"**_)
   - [SCM-696](https://issues.apache.org/jira/browse/SCM-696) SVN tagging fails 
with svn+ssh://username@host URL
   
   




> SVN branching fails with svn+ssh://username@host URL
> ----------------------------------------------------
>
>                 Key: SCM-730
>                 URL: https://issues.apache.org/jira/browse/SCM-730
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.8.1
>            Reporter: Raúl Wegmann
>            Priority: Major
>
> Similar to SCM-696, SVN branching (e.g. when executing {{mvn 
> release:branch}}) is failing when using a svn+ssh://username@host style URL.
> See 
> https://github.com/rwegmann/maven-scm/commit/1193d2946a9a357462e5465c83c56b3a545e257d
>  with the one-line patch. 
> There may be other instances where the URL might require "fixing", but I 
> sadly do not have time to look into it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to