Filter fail to initialize when build from parent pom while assembly is in child pom

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 2.2-beta-2
  • Fix Version/s: None
  • Labels:
    None
  • Environment:
    maven 2.0.9 Windows XP

Description

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..."

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-230 <fileset> not filtering resources, but <files> does filter

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-293 <fileSets> not filtered in multimodule build, but <files> are

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MASSEMBLY-154 FileSet does not support filtering

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jeff Johnson added a comment -

Maven project which illustrates <filtered> working with <file> but not <fileSet>.

Show
Jeff Johnson added a comment - Maven project which illustrates <filtered> working with <file> but not <fileSet>.
Hide
Permalink
Jeff Johnson added a comment -

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 <filtered> works with <file> elements but not with <fileSet> elements.
When running from the child module POM both <file> and <fileSet> 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".

Show
Jeff Johnson added a comment - 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 <filtered> works with <file> elements but not with <fileSet> elements. When running from the child module POM both <file> and <fileSet> 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".
Hide
Permalink
Jeff Johnson added a comment -

These issues are fixed in version 2.2-beta-3, so this issue can be closed.

Show
Jeff Johnson added a comment - These issues are fixed in version 2.2-beta-3, so this issue can be closed.
Hide
Permalink
John Casey added a comment -

checked this against 2.2-beta-5, and it's not failing. It appears to be fixed in the interim.

Show
John Casey added a comment - checked this against 2.2-beta-5, and it's not failing. It appears to be fixed in the interim.

People

  • Assignee:
    John Casey
    Reporter:
    Andy Yeung
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: