You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2019/09/10 13:45:00 UTC
[jira] [Comment Edited] (SCM-883) ScmFileSet DEFAULT_EXCLUDES too
restrictive
[ https://issues.apache.org/jira/browse/SCM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926651#comment-16926651 ]
Konrad Windszus edited comment on SCM-883 at 9/10/19 1:44 PM:
--------------------------------------------------------------
Why is changing the default excludes problematic? I guess including .gitignore in the default excludes is never intended! I opened https://github.com/codehaus-plexus/plexus-utils/issues/71 to track that.
was (Author: kwin):
Why is changing the default excludes problematic? I guess including .gitignore in the default excludes is never intended!
> 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
(v8.3.2#803003)