[
https://issues.apache.org/jira/browse/MASSEMBLY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345156#comment-15345156
]
Seth Leger commented on MASSEMBLY-505:
--------------------------------------
Yes, it is annoying that the documentation claims that this is already
implemented. However, it only works (according to the XSD) for dependencySets.
> Feature Request: useStrictFiltering option for FileSets
> -------------------------------------------------------
>
> Key: MASSEMBLY-505
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-505
> Project: Maven Assembly Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Environment: Maven 2.2.1, RHEL4
> Reporter: John Casey
> Attachments: fail_strictfiltering.zip
>
>
> *NOTE:* This is a clone of MASSEMBLY-488. The original issue will be closed
> Won't Fix, since the plexus-utils class DirectoryScanner, which is the core
> of the FileSet functionality, doesn't support strict include/exclude
> filtering.
> This issue is a feature request to have that added.
> ---------
> I'm trying to turn on useStrictFiltering in a fileSet in an assembly
> descriptor, but maven doesn't fail when the file does not exist. Here
> is an example of what the assembly descriptor looks like:
> <?xml version="1.0" encoding="UTF-8"?><assembly>
> <formats>
> <format>tar.gz</format>
> </formats>
> <fileSets>
> <fileSet>
> <useStrictFiltering>true</useStrictFiltering>
> <directory>src/main</directory>
> <includes>
> <include>nonexistant.txt*</include>
> </includes>
> </fileSet>
> </fileSets>
> </assembly>
> Running "mvn package" happily produces a tarball with no indication that
> anything is wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
