[
https://issues.apache.org/jira/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962822#comment-17962822
]
ASF GitHub Bot commented on SCM-754:
------------------------------------
jira-importer opened a new issue, #948:
URL: https://github.com/apache/maven-scm/issues/948
**[Dan
Tran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=danttran)**
opened
**[SCM-754](https://issues.apache.org/jira/browse/SCM-754?redirect=false)** and
commented
Currently the tag command when using with ScmFileSet that has no
excludes/includes, it returns the entire file list of the source tree. and the
TCK check for it
It makes sense for ScmFileSet with a know list, but not practical when the
list is empty. It can blew up memory and slow for a large source tree.
We should allow this exception
---
**Affects:** 1.9
> Require Tag/Branch Command to return the entire source tree is impractical
> --------------------------------------------------------------------------
>
> Key: SCM-754
> URL: https://issues.apache.org/jira/browse/SCM-754
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-tck
> Affects Versions: 1.9
> Reporter: Dan Tran
> Assignee: Dan Tran
> Priority: Major
> Fix For: 1.9.1
>
>
> Currently the tag command when using with ScmFileSet that has no
> excludes/includes, it returns the entire file list of the source tree. and
> the TCK check for it
> It makes sense for ScmFileSet with a know list, but not practical when the
> list is empty. It can blew up memory and slow for a large source tree.
> We should allow this exception
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
