[
https://issues.apache.org/jira/browse/SCM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963551#comment-17963551
]
ASF GitHub Bot commented on SCM-883:
------------------------------------
jira-importer commented on issue #1117:
URL: https://github.com/apache/maven-scm/issues/1117#issuecomment-2964646816
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
[Köntopp](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=K%C3%B6ntopp),
was lange währt, wird endlich gut!
> ScmFileSet DEFAULT_EXCLUDES too restrictive
> -------------------------------------------
>
> Key: SCM-883
> URL: https://issues.apache.org/jira/browse/SCM-883
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-api
> Affects Versions: 1.9.5
> Reporter: Fabian Köntopp
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 1.12.1, 1.12.2, 2.0.0-M1
>
>
> 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.20.10#820010)
