[
https://issues.apache.org/jira/browse/JCRVLT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277835#comment-17277835
]
Konrad Windszus commented on JCRVLT-495:
----------------------------------------
I am kind of bound with what is provided by Maven OOTB. They only support file
extension filtering (blacklist only). To at least keep it in sync and backwards
compatible also the white list is allowing extensions only. Do you see any
realistic use case, where filtering would do harm for an allowed file
extension. Usually filtering is a Noop on text files when no placeholders are
used. It is only problematic for binary files and those can IMHO be easily
identified via extensions.
> Allow to exclude binaries without extension from filtering
> -----------------------------------------------------------
>
> Key: JCRVLT-495
> URL: https://issues.apache.org/jira/browse/JCRVLT-495
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.1.6
> Reporter: Konrad Windszus
> Priority: Minor
> Fix For: package-maven-plugin-1.1.8
>
>
> In case of simple file aggregates
> (http://jackrabbit.apache.org/filevault/vaultfs.html#Simple_File_aggregates)
> or extended ones the binary has a filename which is equal to the parent node
> name (with type {{nt:file}}). As the node name does not necessarily include a
> dot (e.g. in
> https://github.com/adobe/aem-core-wcm-components/blob/master/examples/ui.content/src/content/jcr_root/content/core-components-examples/_jcr_content/image/file)
> but the file still is a binary which cannot be filtered by Maven, such nodes
> must be excluded.
> Unfortunately leveraging the parameter {{<nonFilteredFileExtensions>}} does
> not work, as Maven does not support empty string entries in Lists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
