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

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

jira-importer commented on issue #431:
URL: https://github.com/apache/maven-scm/issues/431#issuecomment-2964594115

   **[Torbjorn Eikli 
Smorgrav](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=smorgrav)**
 commented
   
   I cannot reproduce the junit error, but from the output given by Emmanuel 
Venisse  I saw that the initial repository where empty.
   I'll add a patch that makes that initial step more robust by forcing 
non-recursive add and by always use absolute paths.
   




> New SCM Provider: Bazaar
> ------------------------
>
>                 Key: SCM-143
>                 URL: https://issues.apache.org/jira/browse/SCM-143
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: New Feature
>         Environment: Tested by junit tests on windows and by continuum on 
> linux.
>            Reporter: Torbjorn Eikli Smorgrav
>            Assignee: Emmanuel Venisse
>            Priority: Minor
>             Fix For: 1.0-beta-3
>
>         Attachments: MNG-143-maven-core.patch, MNG-Bazaar-maven-scm.patch
>
>
> Bazaar is a distributed system developed at http://bazaar.canonical.com/
> The implementation has a few issues: 
> - The diff unit test has been removed due to a subtile issue in the unified 
> diff output.
> -  I have not tested too much with different repository urls eg sftp.



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

Reply via email to