[
http://jira.codehaus.org/browse/MASSEMBLY-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145930#action_145930
]
Petar Tahchiev commented on MASSEMBLY-293:
------------------------------------------
Hi Torsten,
this bus seems to be exactly the same as the 237 one. To avoid this behaviour
you have to specify absolute path to the
directory in your fileset. Just like:
<fileSet>
<directory>${basedir}/src/main/res</directory>
<outputDirectory/>
<filtered>true</filtered>
<includes>
<include>**/*.bat</include>
<include>**/*.sh</include>
</includes>
</fileSet>
here I have specified the ${basedir} and then the rest of the directory.
Or another solution would be to execute your build from the level of your child
module.
I don't think anything needs to be committed on the assembly plugin.
HTH, Petar.
> <fileSets> not filtered in multimodule build, but <files> are
> -------------------------------------------------------------
>
> Key: MASSEMBLY-293
> URL: http://jira.codehaus.org/browse/MASSEMBLY-293
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: Windows XP
> Reporter: Torsten Reinhard
> Fix For: 2.2-beta-3
>
> Attachments: install.xml, update-db2.sh
>
>
> Filtering doesn´t work in a multimodule build if I use <fileSet> instead of
> <files> - if I build the module separately, it works....
> Shouldn´t the behaviour be the same? I have not looked into the code, but I
> expect one thing is collection the files (however the filelist is expressed),
> the other is filtering them. It seems, as the separation of functionality is
> mixed in here?
> See the attached file(s) as example.
--
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
