[jira] Commented: (MASSEMBLY-329) Filter fail to initialize when build from parent pom while assembly is in child pom
[ http://jira.codehaus.org/browse/MASSEMBLY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163467#action_163467 ] Jeff Johnson commented on MASSEMBLY-329: These issues are fixed in version 2.2-beta-3, so this issue can be closed. > Filter fail to initialize when build from parent pom while assembly is in > child pom > --- > > Key: MASSEMBLY-329 > URL: http://jira.codehaus.org/browse/MASSEMBLY-329 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: maven 2.0.9 Windows XP >Reporter: Andy Yeung > Attachments: maven-assembly-plugin-bug-filtered.zip, > project-structure.zip, target-aggregator.zip, target-module.zip > > > I have the project structure which is the same as the attached file. When I > try to execute mvn package in the user-ear project directly, the filters are > initialized and executed. However if I try to execute mvn package in the > parent directory. The filter is gone. When I use -X options, I didn't find > the log message > "[DEBUG] Initializing assembly filters..." -- 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-329) Filter fail to initialize when build from parent pom while assembly is in child pom
[ http://jira.codehaus.org/browse/MASSEMBLY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Johnson updated MASSEMBLY-329: --- Attachment: target-module.zip target-aggregator.zip > Filter fail to initialize when build from parent pom while assembly is in > child pom > --- > > Key: MASSEMBLY-329 > URL: http://jira.codehaus.org/browse/MASSEMBLY-329 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: maven 2.0.9 Windows XP >Reporter: Andy Yeung > Attachments: maven-assembly-plugin-bug-filtered.zip, > project-structure.zip, target-aggregator.zip, target-module.zip > > > I have the project structure which is the same as the attached file. When I > try to execute mvn package in the user-ear project directly, the filters are > initialized and executed. However if I try to execute mvn package in the > parent directory. The filter is gone. When I use -X options, I didn't find > the log message > "[DEBUG] Initializing assembly filters..." -- 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-329) Filter fail to initialize when build from parent pom while assembly is in child pom
[ http://jira.codehaus.org/browse/MASSEMBLY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163466#action_163466 ] Jeff Johnson commented on MASSEMBLY-329: I have experienced the same issue and have a few more details. Please see attachment "maven-assembly-plugin-bug-filtered.zip". When running from the parent aggregator POM works with elements but not with elements. When running from the child module POM both and elements are properly filtered. Note that when running from the child module POM the resulting target/archive-tmp directory contains fileSetFormatter.*.tmp directories, but not when running from the parent aggregator POM. I will attach the resulting target directories as "target-aggregator.zip" and "target-module.zip". > Filter fail to initialize when build from parent pom while assembly is in > child pom > --- > > Key: MASSEMBLY-329 > URL: http://jira.codehaus.org/browse/MASSEMBLY-329 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: maven 2.0.9 Windows XP >Reporter: Andy Yeung > Attachments: maven-assembly-plugin-bug-filtered.zip, > project-structure.zip > > > I have the project structure which is the same as the attached file. When I > try to execute mvn package in the user-ear project directly, the filters are > initialized and executed. However if I try to execute mvn package in the > parent directory. The filter is gone. When I use -X options, I didn't find > the log message > "[DEBUG] Initializing assembly filters..." -- 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-329) Filter fail to initialize when build from parent pom while assembly is in child pom
[ http://jira.codehaus.org/browse/MASSEMBLY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Johnson updated MASSEMBLY-329: --- Attachment: maven-assembly-plugin-bug-filtered.zip Maven project which illustrates working with but not . > Filter fail to initialize when build from parent pom while assembly is in > child pom > --- > > Key: MASSEMBLY-329 > URL: http://jira.codehaus.org/browse/MASSEMBLY-329 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: maven 2.0.9 Windows XP >Reporter: Andy Yeung > Attachments: maven-assembly-plugin-bug-filtered.zip, > project-structure.zip > > > I have the project structure which is the same as the attached file. When I > try to execute mvn package in the user-ear project directly, the filters are > initialized and executed. However if I try to execute mvn package in the > parent directory. The filter is gone. When I use -X options, I didn't find > the log message > "[DEBUG] Initializing assembly filters..." -- 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-327) Using filtered within dependencySet unpackOptions
[ http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162838#action_162838 ] Jeff Johnson commented on MASSEMBLY-327: This is a significant missing feature. > 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 > > > > src/assemble/filter.properties > > > which contains >storage.id=abcde > assembly.xml defines dependency set > > /snp-agent1 > true > > true > > runtime > > > XXX.agent:agent-ear-config > > > > 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
