[
http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164541#action_164541
]
Matt Innes commented on MASSEMBLY-327:
--------------------------------------
As per the other comments - I designed my whole build process around filtering
dependencySets and I will now have to do a significant amount of refactoring to
get it to work. I've taken a look at the code and it's a non-trivial task
which is presumably why it hasn't been done yet. If someone with Maven dev
knowledge were able to point me in the right direction for fixing this I might
give it a go. The existing filtering code applies to files only - I presume
this would have to change to operate on streams, or the dependencySet assembly
would have to go through an interim file stage ...
> Using filtered within dependencySet unpackOptions
> -------------------------------------------------
>
> Key: MASSEMBLY-327
> URL: http://jira.codehaus.org/browse/MASSEMBLY-327
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Reporter: Andy Yeung
>
> The files within the unpacked jar did not apply the filters defined.
> pom configuration includes
> <configuration>
> <filters>
>
> <filter>src/assemble/filter.properties</filter>
> </filters>
> </configuration>
> which contains
> storage.id=abcde
> assembly.xml defines dependency set
> <dependencySet>
> <outputDirectory>/snp-agent1</outputDirectory>
> <unpack>true</unpack>
> <unpackOptions>
> <filtered>true</filtered>
> </unpackOptions>
> <scope>runtime</scope>
> <includes>
> <include>
> XXX.agent:agent-ear-config
> </include>
> </includes>
> </dependencySet>
> However, the files within 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
