[
https://issues.apache.org/jira/browse/MNG-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8477:
---------------------------------
Fix Version/s: 4.0.0-rc-3
> File-activated profile not activated when maven.modelBuilder.parallelism=1
> --------------------------------------------------------------------------
>
> Key: MNG-8477
> URL: https://issues.apache.org/jira/browse/MNG-8477
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-rc-2
> Reporter: Dmitry Kichinsky
> Priority: Major
> Fix For: 4.0.0-rc-3
>
> Attachments: project.zip
>
>
> *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.
> {code:java}
> Active Profiles for Project 'test:m2:jar:1':
> The following profiles are active:
> - xxx (source: test:m2:jar:1){code}
> However, when running {{{}mvn help:active-profiles
> -Dmaven.modelBuilder.parallelism=1{}}}, the "xxx" profile fails to activate.
> {code:java}
> Active Profiles for Project 'test:m2:jar:1':
> The following profiles are active: {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
