Skip to content

[MNG-8736] Incorrect profile activation for multi-module concurrent build #9563

@jira-importer

Description

@jira-importer

Mateusz Gajewski opened MNG-8736 and commented

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

 


Affects: 4.0.0-rc-3

Attachments:

Remote Links:

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority:majorMajor loss of function

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions