You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Liya Jan (JIRA)" <ji...@codehaus.org> on 2007/05/01 22:36:26 UTC
[jira] Created: (MASSEMBLY-206) Filtering does not work when using
in fileSet inside moduleSet
Filtering does not work when using in fileSet inside moduleSet
--------------------------------------------------------------
Key: MASSEMBLY-206
URL: http://jira.codehaus.org/browse/MASSEMBLY-206
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: win32
Reporter: Liya Jan
i have a descriptor :
<moduleSet>
<includes>
<include>com.cc:module1</include>
<include>com.cc:module2</include>
<include>com.cc:module3</include>
</includes>
<sources>
<fileSets>
<fileSet>
<directory>src/main</directory>
<filtered>true</filtered>
<outputDirectory>core</outputDirectory>
<includes>
<include>conf/*</include>
</includes>
</fileSet>
</fileSets>
<includeModuleDirectory>false</includeModuleDirectory>
</sources>
</moduleSet>
and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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-206) Filtering does not work when using
in fileSet inside moduleSet
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-206:
---------------------------------
Fix Version/s: 2.2
> Filtering does not work when using in fileSet inside moduleSet
> --------------------------------------------------------------
>
> Key: MASSEMBLY-206
> URL: http://jira.codehaus.org/browse/MASSEMBLY-206
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: win32
> Reporter: Liya Jan
> Fix For: 2.2
>
>
> i have a descriptor :
> <moduleSet>
> <includes>
> <include>com.cc:module1</include>
> <include>com.cc:module2</include>
> <include>com.cc:module3</include>
> </includes>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src/main</directory>
> <filtered>true</filtered>
> <outputDirectory>core</outputDirectory>
> <includes>
> <include>conf/*</include>
> </includes>
> </fileSet>
> </fileSets>
> <includeModuleDirectory>false</includeModuleDirectory>
> </sources>
> </moduleSet>
> and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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-206) Filtering does not work when
using in fileSet inside moduleSet
Posted by "Kevin Stembridge (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98846 ]
Kevin Stembridge commented on MASSEMBLY-206:
--------------------------------------------
Looks like a duplicate of MASSEMBLY-154
> Filtering does not work when using in fileSet inside moduleSet
> --------------------------------------------------------------
>
> Key: MASSEMBLY-206
> URL: http://jira.codehaus.org/browse/MASSEMBLY-206
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: win32
> Reporter: Liya Jan
>
> i have a descriptor :
> <moduleSet>
> <includes>
> <include>com.cc:module1</include>
> <include>com.cc:module2</include>
> <include>com.cc:module3</include>
> </includes>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src/main</directory>
> <filtered>true</filtered>
> <outputDirectory>core</outputDirectory>
> <includes>
> <include>conf/*</include>
> </includes>
> </fileSet>
> </fileSets>
> <includeModuleDirectory>false</includeModuleDirectory>
> </sources>
> </moduleSet>
> and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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-206) Filtering does not work when using
in fileSet inside moduleSet
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-206.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2)
2.2-beta-6
Assignee: John Casey
> Filtering does not work when using in fileSet inside moduleSet
> --------------------------------------------------------------
>
> Key: MASSEMBLY-206
> URL: http://jira.codehaus.org/browse/MASSEMBLY-206
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: win32
> Reporter: Liya Katz
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> i have a descriptor :
> <moduleSet>
> <includes>
> <include>com.cc:module1</include>
> <include>com.cc:module2</include>
> <include>com.cc:module3</include>
> </includes>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src/main</directory>
> <filtered>true</filtered>
> <outputDirectory>core</outputDirectory>
> <includes>
> <include>conf/*</include>
> </includes>
> </fileSet>
> </fileSets>
> <includeModuleDirectory>false</includeModuleDirectory>
> </sources>
> </moduleSet>
> and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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-206) Filtering does not work when
using in fileSet inside moduleSet
Posted by "serxio (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97672 ]
serxio commented on MASSEMBLY-206:
----------------------------------
Also fails outside moduleSet. This is my descriptor:
<assembly>
<id>SNAPSHOT</id>
<formats>
<format>tar.gz</format>
</formats>
<moduleSets>
<moduleSet>
<binaries>
<includeDependencies>true</includeDependencies>
</binaries>
</moduleSet>
</moduleSets>
<fileSets>
<fileSet>
<includes>
<include>README*</include>
<include>LICENSE*</include>
<include>NOTICE*</include>
</includes>
</fileSet>
<fileSet>
<directory>target</directory>
<outputDirectory>lib</outputDirectory>
<includes>
<include>*.jar</include>
</includes>
</fileSet>
<fileSet>
<directory>src/main/bin</directory>
<outputDirectory>bin</outputDirectory>
<includes>
<include>*</include>
</includes>
<filtered>true</filtered>
<lineEnding>unix</lineEnding>
<fileMode>0744</fileMode>
</fileSet>
<fileSet>
<directory>src/main/config</directory>
<outputDirectory>config</outputDirectory>
<includes>
<include>*</include>
</includes>
<filtered>true</filtered>
<lineEnding>unix</lineEnding>
<fileMode>0644</fileMode>
</fileSet>
</fileSets>
</assembly>
> Filtering does not work when using in fileSet inside moduleSet
> --------------------------------------------------------------
>
> Key: MASSEMBLY-206
> URL: http://jira.codehaus.org/browse/MASSEMBLY-206
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: win32
> Reporter: Liya Jan
>
> i have a descriptor :
> <moduleSet>
> <includes>
> <include>com.cc:module1</include>
> <include>com.cc:module2</include>
> <include>com.cc:module3</include>
> </includes>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src/main</directory>
> <filtered>true</filtered>
> <outputDirectory>core</outputDirectory>
> <includes>
> <include>conf/*</include>
> </includes>
> </fileSet>
> </fileSets>
> <includeModuleDirectory>false</includeModuleDirectory>
> </sources>
> </moduleSet>
> and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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-206) Filtering does not work when
using in fileSet inside moduleSet
Posted by "Helge Olav Aarstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179769#action_179769 ]
Helge Olav Aarstein commented on MASSEMBLY-206:
-----------------------------------------------
Have a similar problem on a multi-module project using a re-usable assembly descriptor:
Filtering works fine on <file> elements across the modules, but the variables are not expanded on <fileSet> elements if mvn package is executed on the parent project.
> Filtering does not work when using in fileSet inside moduleSet
> --------------------------------------------------------------
>
> Key: MASSEMBLY-206
> URL: http://jira.codehaus.org/browse/MASSEMBLY-206
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: win32
> Reporter: Liya Katz
> Fix For: 2.2
>
>
> i have a descriptor :
> <moduleSet>
> <includes>
> <include>com.cc:module1</include>
> <include>com.cc:module2</include>
> <include>com.cc:module3</include>
> </includes>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src/main</directory>
> <filtered>true</filtered>
> <outputDirectory>core</outputDirectory>
> <includes>
> <include>conf/*</include>
> </includes>
> </fileSet>
> </fileSets>
> <includeModuleDirectory>false</includeModuleDirectory>
> </sources>
> </moduleSet>
> and although there is "<filtered>true</filtered>", the copied sources are not filtered.
--
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