[
http://jira.codehaus.org/browse/MASSEMBLY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253156#action_253156
]
R.M.Morrien commented on MASSEMBLY-505:
---------------------------------------
With 2.2-beta-5 I have the problem as described.
With 2.2 I run into:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2:single (make-assembly) on
project testassembly: Error reading
assemblies: Error reading descriptor:
/src/main/resources/assemblies/assembly.xml: Unrecognised tag:
'useStrictFiltering' (position: START
_TAG seen ...<fileSet>\r\n <useStrictFiltering>... @11:33) -> [Help
1]
For me useStrictFiltering is mandatory to ensure correct release build
assemblies.
> Feature Request: useStrictFiltering option for FileSets
> -------------------------------------------------------
>
> Key: MASSEMBLY-505
> URL: http://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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
