You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Haszlakiewicz (JIRA)" <ji...@codehaus.org> on 2010/09/27 17:34:32 UTC
[jira] Commented: (MASSEMBLY-488) restrict useStrictFiltering
option to DependencySets
[ http://jira.codehaus.org/browse/MASSEMBLY-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236607#action_236607 ]
Eric Haszlakiewicz commented on MASSEMBLY-488:
----------------------------------------------
So, does this mean that the assembly descriptor I tried would cause an error and cause the build to fail because of an "unknown" useStrictFiltering element? Although that's obviously not as ideal as actually making it work, that would certainly be better than just silently ignoring it.
> restrict useStrictFiltering option to DependencySets
> ----------------------------------------------------
>
> Key: MASSEMBLY-488
> URL: http://jira.codehaus.org/browse/MASSEMBLY-488
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-5
> Environment: Maven 2.2.1, RHEL4
> Reporter: Eric Haszlakiewicz
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
> Attachments: fail_strictfiltering.zip
>
>
> *NOTE:* Currently there is no good way to support strict filtering of fileSets. This feature should be restricted to DependencySets.
> I'll clone this issue to express the interest in re-adding this as a new feature with support from the plexus-utils DirectoryScanner, which much support strict filtering first.
> ---------
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira