[
https://issues.apache.org/jira/browse/SCM-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961981#comment-17961981
]
ASF GitHub Bot commented on SCM-540:
------------------------------------
jira-importer opened a new issue, #751:
URL: https://github.com/apache/maven-scm/issues/751
**[Dan
Tran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dantran)**
opened
**[SCM-540](https://issues.apache.org/jira/browse/SCM-540?redirect=false)** and
commented
Current, scm:checkout and scm:export allows excludes/includes configuration.
However these params are ignored.
We should perform the filter (remove necessary files ) after scm action
complete.
The question here: should it be done at plugin level or api level.
This use case is a good feature to have, rather having the user to use
antrun to do the post filter
---
**Affects:** 1.3
**Issue Links:**
- [SCM-526](https://issues.apache.org/jira/browse/SCM-526) scm:checkout and
scm:export ignores excludes and includes configuration
(_**"duplicates"**_)
> Hornor scm:checkout scm:export's excludes/includes configuration
> ----------------------------------------------------------------
>
> Key: SCM-540
> URL: https://issues.apache.org/jira/browse/SCM-540
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Affects Versions: 1.3
> Environment: all
> Reporter: Dan Tran
> Priority: Major
>
> Current, scm:checkout and scm:export allows excludes/includes configuration.
> However these params are ignored.
> We should perform the filter (remove necessary files ) after scm action
> complete.
> The question here: should it be done at plugin level or api level.
> This use case is a good feature to have, rather having the user to use antrun
> to do the post filter
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
