[
https://issues.apache.org/jira/browse/MNG-8736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8736:
---------------------------------
Fix Version/s: 4.0.0-rc-4
> Incorrect profile activation for multi-module concurrent build
> --------------------------------------------------------------
>
> Key: MNG-8736
> URL: https://issues.apache.org/jira/browse/MNG-8736
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.0.0-rc-3
> Reporter: Mateusz Gajewski
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-rc-4
>
> Attachments: debug.log
>
>
> This happens on: *4.0.0-rc3*
> Doesn't happen on: *3.9.9*
> {*}Parent pom{*}:
> https://github.com/airlift/airbase/blob/master/airbase/pom.xml#L1747
> In our base pom we have a profile with activation based on the existence of
> the file in the project module ({{{}.build-airlift{}}}). While building
> project concurrently under maven 4.0.0-rc3, the profile is activated for
> module lacking {{.build-airlift}} file (which is signaled by the enforcer
> maven plugin that checks for the existence of the main-class property).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
