[MENFORCER-226] requireActiveProfile ignores inherited profiles in submoduless

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 1.4
• Component/s: Standard Rules
• Environment: Maven 3.2.2, JDK 7, Windows 7 64bit
• Assignee: Robert Scholte
• Reporter: Yago Méndez Vidal
• Created: 25/Feb/15 02:58
• Updated: 26/May/21 18:31
• Resolved: 26/May/21 18:31

Description

When having a POM project with modules, using the requireActiveProfile rule on one of the modules fails to resolve profiles that are inherited from the parent.

I've attached 2 POMs to reproduce the problem:

• parent project defines a profile called one and enforces it to be active
• submodule does nothing, just inherits both

When ran with -P one parameter we get on the submodule (not the parent pom, which works fine):
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireActiveProfile failed with message:
Profile "one" is not activated.

If we run mvn -P one help:active-profiles we can observe that the profile is effectively activated on the submodule:
Active Profiles for Project 'example:-maven-subproject:jar:0.0.1-SNAPSHOT':

The following profiles are active:

- default (source: external)
- one (source: example:test-maven-project:0.0.1-SNAPSHOT)

Issue Links

• duplicates: MENFORCER-257 RequireActiveProfile should respect inherited activated profiles
• relates to: MPH-94 MavenProject.getActiveProfiles() does not merge active profiles from parent POMs