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

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

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

   **[Ringo De 
Smet](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ringods)** 
opened 
**[SCM-440](https://issues.apache.org/jira/browse/SCM-440?redirect=false)** and 
commented
   
   The includes and excludes properties are not used when running scm:update. 
Attached you can find a patch that already resolves this for the CVS 
provider(s). I tested it on my local setup and it worked as expected.
   
   
   ---
   
   **Affects:** 1.1
   
   **Attachments:**
   - 
[cvs-update-includes-patch.txt](https://issues.apache.org/jira/secure/attachment/12718849/cvs-update-includes-patch.txt)
 (_1.18 kB_)
   




> <includes> and <excludes> do not seem to work correctly during scm:update
> -------------------------------------------------------------------------
>
>                 Key: SCM-440
>                 URL: https://issues.apache.org/jira/browse/SCM-440
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-accurev, maven-scm-provider-bazaar, 
> maven-scm-provider-clearcase, maven-scm-provider-cvs, 
> maven-scm-provider-gitexe, maven-scm-provider-local, 
> maven-scm-provider-mercurial (hg), maven-scm-provider-monotone, 
> maven-scm-provider-perforce, maven-scm-provider-pvcs, 
> maven-scm-provider-starteam, maven-scm-provider-svn, 
> maven-scm-provider-synergy, maven-scm-provider-vss
>    Affects Versions: 1.1
>            Reporter: Ringo De Smet
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 1.2
>
>         Attachments: cvs-update-includes-patch.txt
>
>
> The includes and excludes properties are not used when running scm:update. 
> Attached you can find a patch that already resolves this for the CVS 
> provider(s). I tested it on my local setup and it worked as expected.



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

Reply via email to