[MRELEASE-415] Plugin fails to activate profiles in submodules.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-8
• Fix Version/s: 2.4
• Component/s: perform
• Environment: Fedora8, Sun Java 1.6.0_07, Maven 2.0.9
• Assignee: Robert Scholte
• Reporter: David C. Hicks
• Created: 19/Feb/09 11:19
• Updated: 19/Nov/12 14:17
• Resolved: 19/Nov/12 14:17

Description

(I hope this is not a duplicate. I searched JIRA but didn't find anything that looked like one.)

In a multi-module project, profiles that are activated only for sub-modules (not the parent project) are omitted from execution during release:perform. In my specific case, I have a large, multi-module project in which one of the sub-modules is there to create an assembly during release. Since I only want it to run during release, I've placed that into a profile in the sub-module's pom.xml. When I run release:perform, I activate the profile. However, the profile is never executed.

Workaround: By adding a dummy profile to the parent pom.xml, I was able to get release:perform to operate as desired.

I'm afraid I don't have an example to upload, at this time. If I can find the time, I'll try to create one and come back to upload it.

Issue Links

• is related to: MRELEASE-571 When collecting active profiles, the active profiles from parent poms are not considered