Dmitry Kichinsky opened MNG-8477 and commented
Reproducer project (attached)
In a multi-module project with a parent POM ({}project{}) and two child modules ({}m1{} and {}m2{}), the parent POM defines a profile named "xxx" that is activated by the presence of a file ({}src/io.properties{}). The file triggering the profile ({}io.properties{}) is placed under {}m2/src/{}, satisfying the activation condition in {}m2{}.
Steps to reproduce
In Maven 4.0.0-rc-2, running mvn help:active-profiles correctly identifies the "xxx" profile as active.
Active Profiles for Project 'test:m2:jar:1':
The following profiles are active:
- xxx (source: test:m2:jar:1)
However, when running {}mvn help:active-profiles -Dmaven.modelBuilder.parallelism=1{}, the "xxx" profile fails to activate.
Active Profiles for Project 'test:m2:jar:1':
The following profiles are active:
Affects: 4.0.0-rc-2
Attachments:
Remote Links:
Dmitry Kichinsky opened MNG-8477 and commented
Reproducer project (attached)
In a multi-module project with a parent POM (
{}project{}) and two child modules ({}m1{} and{}m2{}), the parent POM defines a profile named "xxx" that is activated by the presence of a file ({}src/io.properties{}). The file triggering the profile ({}io.properties{}) is placed under{}m2/src/{}, satisfying the activation condition in{}m2{}.Steps to reproduce
In Maven 4.0.0-rc-2, running
mvn help:active-profilescorrectly identifies the "xxx" profile as active.However, when running
{}mvn help:active-profiles -Dmaven.modelBuilder.parallelism=1{}, the "xxx" profile fails to activate.Affects: 4.0.0-rc-2
Attachments:
Remote Links: