You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jonas Berlin (JIRA)" <ji...@codehaus.org> on 2012/09/20 10:05:21 UTC
[jira] (MASSEMBLY-505) Feature Request: useStrictFiltering option
for FileSets
[ https://jira.codehaus.org/browse/MASSEMBLY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309195#comment-309195 ]
Jonas Berlin commented on MASSEMBLY-505:
----------------------------------------
The same issue occurs also when the {{<directory>...</directory>}} specified does not exist. I hope the implementation will check for this as well.
> Feature Request: useStrictFiltering option for FileSets
> -------------------------------------------------------
>
> Key: MASSEMBLY-505
> URL: https://jira.codehaus.org/browse/MASSEMBLY-505
> Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira