You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mick Knutson (JIRA)" <ji...@codehaus.org> on 2007/08/17 18:48:47 UTC
[jira] Created: (MASSEMBLY-230) not filtering resources,
but does filter
<fileset> not filtering resources, but <files> does filter
----------------------------------------------------------
Key: MASSEMBLY-230
URL: http://jira.codehaus.org/browse/MASSEMBLY-230
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: Windows XP Maven 2.0.5
Reporter: Mick Knutson
In my assembly descriptor, this does not filter my resources:
<fileSet>
<directory>${basedir}/src/main/resources/deploy</directory>
<filtered>true</filtered>
<useStrictFiltering>true</useStrictFiltering>
<outputDirectory>/</outputDirectory>
<includes>
<include>*.sh</include>
<include>*.bat</include>
</includes>
<fileMode>0544</fileMode>
</fileSet>
But this DOES filter the same resources just fine:
<files>
<file>
<source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
<outputDirectory>deploy</outputDirectory>
<destName>test.sh</destName>
<filtered>true</filtered>
<lineEnding>unix</lineEnding>
<fileMode>0554</fileMode>
</file>
</files>
I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Jon Travis (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272418#comment-272418 ]
Jon Travis commented on MASSEMBLY-230:
--------------------------------------
FWIW, I am still seeing this in Maven 2.2.1
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: https://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MASSEMBLY-230) not
filtering resources, but does filter
Posted by "Oleg Alexeyev (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135195#action_135195 ]
blacklion edited comment on MASSEMBLY-230 at 5/16/08 4:45 PM:
------------------------------------------------------------------
According to my experiments, fileSets filter files ok when a sub-module in a multi-module project is being built directly. But they do not filter files properly if I build a parent project.
Does anybody have a workaround for that other than using individual files?
was (Author: blacklion):
According to my experiments, fileSets filter files ok when a sub-module in a multi-module project is being built directly. But they do not filter files properly if I build a parent project.
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144940#action_144940 ]
Bugittaa Pahasti commented on MASSEMBLY-230:
--------------------------------------------
Yes, works ok when building the assembly module only, but not when building from parent.
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Robert Weissmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145003#action_145003 ]
Robert Weissmann commented on MASSEMBLY-230:
--------------------------------------------
Bugittaa Pahasti as Oleg Alexeyev said already before...
We still wait for a fix so doing it from a parent would make it work too.
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Robert Weissmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118373 ]
Robert Weissmann commented on MASSEMBLY-230:
--------------------------------------------
Hi,
I got the same problem as well and there is no way to mention all files individually.
Remark: Don't get confused on the ending .txt in "${basedir}/src/main/resources/deploy/deploy.sh.txt" from the example. It might be typo. But it really does not work in my case too.
Here is my code-snippet:
Does not work:
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<includes>
<include>**/*.xml</include>
</includes>
<filtered>true</filtered>
</fileSet>
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
<filtered>false</filtered>
</fileSet>
Works:
<files>
<file>
<source>cfg/JustA6TestConfig.xml</source>
<outputDirectory>cfg</outputDirectory>
<filtered>true</filtered>
</file>
</files>
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Kirill Petrov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141295#action_141295 ]
Kirill Petrov commented on MASSEMBLY-230:
-----------------------------------------
I have exact same problem, it does not filter if I build parent project. Very annoying.
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Oleg Alexeyev (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135195#action_135195 ]
Oleg Alexeyev commented on MASSEMBLY-230:
-----------------------------------------
According to my experiments, fileSets filter files ok when a sub-module in a multi-module project is being built directly. But they do not filter files properly if I build a parent project.
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Updated: (MASSEMBLY-230) not filtering resources,
but does filter
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-230:
---------------------------------
Fix Version/s: 2.2
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Commented: (MASSEMBLY-230) not filtering
resources, but does filter
Posted by "Luc Willems (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148640#action_148640 ]
Luc Willems commented on MASSEMBLY-230:
---------------------------------------
same issues here , multi-module project , assembly works in module build but not from parent build
using 2.0.9 on OpenSUSE 11
any news on this or work around ?
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Issue Comment Edited: (MASSEMBLY-230) not
filtering resources, but does filter
Posted by "Robert Weissmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118373 ]
robert.weissmann edited comment on MASSEMBLY-230 at 1/2/08 2:54 AM:
--------------------------------------------------------------------
Hi,
I got the same problem as well and there is no way to mention all files individually.
Remark: Don't get confused on the ending .txt in "${basedir}/src/main/resources/deploy/deploy.sh.txt" from the example. It might be typo. But it really does not work in my case too.
Here is my code-snippet:
Does not work:
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<includes>
<include>**/*.xml</include>
</includes>
<filtered>true</filtered>
</fileSet>
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
<filtered>false</filtered>
</fileSet>
Works:
<files>
<file>
<source>cfg/JustA6TestConfig.xml</source>
<outputDirectory>cfg</outputDirectory>
<filtered>true</filtered>
</file>
</files>
It looks like there were allready some issues before, which are all marked as Fixed and Closed. Hm, looks like those fixes have been lost again. (Branch-Merging ? ;-).
was (Author: robert.weissmann):
Hi,
I got the same problem as well and there is no way to mention all files individually.
Remark: Don't get confused on the ending .txt in "${basedir}/src/main/resources/deploy/deploy.sh.txt" from the example. It might be typo. But it really does not work in my case too.
Here is my code-snippet:
Does not work:
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<includes>
<include>**/*.xml</include>
</includes>
<filtered>true</filtered>
</fileSet>
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
<filtered>false</filtered>
</fileSet>
Works:
<files>
<file>
<source>cfg/JustA6TestConfig.xml</source>
<outputDirectory>cfg</outputDirectory>
<filtered>true</filtered>
</file>
</files>
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Closed: (MASSEMBLY-230) not filtering resources,
but does filter
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-230.
--------------------------------
Assignee: John Casey
Resolution: Duplicate
Fix Version/s: (was: 2.2)
2.2-beta-3
See MASSEMBLY-293, this is fixed for 2.2-beta-3 (which is headed for a release soonish).
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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
[jira] Issue Comment Edited: (MASSEMBLY-230) not
filtering resources, but does filter
Posted by "Robert Weissmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118373 ]
robert.weissmann edited comment on MASSEMBLY-230 at 1/2/08 2:59 AM:
--------------------------------------------------------------------
Hi,
I got the same problem as well and there is no way to mention all files individually.
Remark: Don't get confused on the ending .txt in "${basedir}/src/main/resources/deploy/deploy.sh.txt" from the example. It might be typo. But it really does not work in my case too.
Here is my code-snippet:
Does not work:
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<includes>
<include>**/*.xml</include>
</includes>
<filtered>true</filtered>
</fileSet>
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
<filtered>false</filtered>
</fileSet>
Works:
<files>
<file>
<source>cfg/JustA6TestConfig.xml</source>
<outputDirectory>cfg</outputDirectory>
<filtered>true</filtered>
</file>
</files>
It looks like there were allready some issues before, which are all marked as Fixed and Closed. Hm, looks like those fixes have been lost again. (Branch-Merging ? ;-).
P.S. Don't get confused, but somehow does this editor by saving the text swollow the STARS in the includes/excludes.
was (Author: robert.weissmann):
Hi,
I got the same problem as well and there is no way to mention all files individually.
Remark: Don't get confused on the ending .txt in "${basedir}/src/main/resources/deploy/deploy.sh.txt" from the example. It might be typo. But it really does not work in my case too.
Here is my code-snippet:
Does not work:
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<includes>
<include>**/*.xml</include>
</includes>
<filtered>true</filtered>
</fileSet>
<fileSet>
<directory>cfg</directory>
<outputDirectory>cfg</outputDirectory>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
<filtered>false</filtered>
</fileSet>
Works:
<files>
<file>
<source>cfg/JustA6TestConfig.xml</source>
<outputDirectory>cfg</outputDirectory>
<filtered>true</filtered>
</file>
</files>
It looks like there were allready some issues before, which are all marked as Fixed and Closed. Hm, looks like those fixes have been lost again. (Branch-Merging ? ;-).
> <fileset> not filtering resources, but <files> does filter
> ----------------------------------------------------------
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
> Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
> <fileSet>
> <directory>${basedir}/src/main/resources/deploy</directory>
> <filtered>true</filtered>
> <useStrictFiltering>true</useStrictFiltering>
> <outputDirectory>/</outputDirectory>
> <includes>
> <include>*.sh</include>
> <include>*.bat</include>
> </includes>
> <fileMode>0544</fileMode>
> </fileSet>
> But this DOES filter the same resources just fine:
> <files>
> <file>
> <source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
> <outputDirectory>deploy</outputDirectory>
> <destName>test.sh</destName>
> <filtered>true</filtered>
> <lineEnding>unix</lineEnding>
> <fileMode>0554</fileMode>
> </file>
> </files>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.
--
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