You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thomas Pischke (Jira)" <ji...@apache.org> on 2021/06/22 13:17:00 UTC
[jira] [Commented] (ARCHETYPE-617) Files in a folder with a file
that has no extension are not filtered
[ https://issues.apache.org/jira/browse/ARCHETYPE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367324#comment-17367324 ]
Thomas Pischke commented on ARCHETYPE-617:
------------------------------------------
This would also be fixed by the PR in ARCHETYPE-548, but that issue is marked as closed.
> Files in a folder with a file that has no extension are not filtered
> --------------------------------------------------------------------
>
> Key: ARCHETYPE-617
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-617
> Project: Maven Archetype
> Issue Type: Bug
> Components: Creator
> Affects Versions: 3.2.0
> Reporter: Thomas Pischke
> Priority: Major
>
> When using create-from-project, the filtering works but the filtered file is later overwritten with the original unfiltered content. The overwrite occurs due to an overly broad fileset (***/**) created due to the presence of a file with no extension in the folder.
> We rely on the secondLevelResourceDirectory structure to include the directory.
> Working on a PR.
> Also broken in 3.2.1-SNAPSHOT
> Example file structure that exhibits the bug:
> * build
> ** docker
> *** Dockerfile
> *** should-be-filtered-but-is-not.yaml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)