[
https://issues.apache.org/jira/browse/ARCHETYPE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Pischke updated ARCHETYPE-617:
-------------------------------------
Description:
When use create-from-project, the filtering works but the filtered file is
later overwritten by an overly eager fileset that replaces it with the
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.
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
was:
The filtering works, but is later overwritten to an overly eager fileset
created due to the presence of a file with no extension.
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
> 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 use create-from-project, the filtering works but the filtered file is
> later overwritten by an overly eager fileset that replaces it with the
> 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.
> 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)
