maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCM-883) ScmFileSet DEFAULT_EXCLUDES too restrictive
Date Sun, 29 Apr 2018 22:34:00 GMT

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

Michael Osipov commented on SCM-883:
------------------------------------

I do agree that these files are regular files need to be managed. [~khmarbaise], any idea
why would should not drop them from {{org.codehaus.plexus.util.AbstractScanner.DEFAULTEXCLUDES}}?
Same applies for Mercurial and CVS.

> ScmFileSet DEFAULT_EXCLUDES too restrictive
> -------------------------------------------
>
>                 Key: SCM-883
>                 URL: https://issues.apache.org/jira/browse/SCM-883
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-api
>    Affects Versions: 1.9.5
>            Reporter: Fabian Köntopp
>            Priority: Minor
>
> We are trying to automate a process in which a default *.gitignore* file *only* (ignoring
the current state of the repository) is added to a repository at the root level. Because
of the DEFAULT_EXCLUDES in the ScmFileSet-Class this is impossible because .gitignore is
listed there and the default excludes are always added to the final exlude list.
> In my opinion the .gitignore file should not be listed there because such files are part
of a git repository. At least it should be possible to override the excludes completely without
the DEFAULT_EXCLUDES always being added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message