You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2010/09/25 00:08:32 UTC
[jira] Updated: (MASSEMBLY-505) Feature Request: useStrictFiltering
option for FileSets
[ http://jira.codehaus.org/browse/MASSEMBLY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-505:
---------------------------------
Description:
*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.
was:
*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.
Affects Version/s: (was: 2.2-beta-5)
2.2-beta-6
Fix Version/s: (was: 2.2-beta-6)
Assignee: (was: John Casey)
Issue Type: New Feature (was: Bug)
> 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-beta-6
> 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