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

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

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

   **[Robert 
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
 opened 
**[SCM-674](https://issues.apache.org/jira/browse/SCM-674?redirect=false)** and 
commented
   
   With these restrictions we have better control over the ScmFiles, so 
projects using SCM don't have to write their own workarounds.
   
   
   ---
   
   **Affects:** 1.7
   
   **Issue Links:**
   - [MRELEASE-764](https://issues.apache.org/jira/browse/MRELEASE-764) Default 
excludes are not recognized by SVNKit SCM provider
   
   
   1 votes, 2 watchers
   




> ScmFile.path should always be relative and never start with any 
> file-separator 
> -------------------------------------------------------------------------------
>
>                 Key: SCM-674
>                 URL: https://issues.apache.org/jira/browse/SCM-674
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-scm-api
>    Affects Versions: 1.7
>            Reporter: Robert Scholte
>            Priority: Minor
>
> With these restrictions we have better control over the ScmFiles, so projects 
> using SCM don't have to write their own workarounds.



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

Reply via email to