[MNG-4120] Profile activation should be per module

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.9
• Component/s: Dependencies, POM
• Assignee: Brett Porter
• Reporter: tinne
• Created: 31/Mar/09 10:19
• Updated: 09/Apr/09 09:19
• Resolved: 09/Apr/09 09:19

Description

In a multi-module-project, one might wish to run certain targets dependent on the existance of some file or directory.

In a single-module-project, I'd say

<profiles><profile><id>do-if-file-exists</id>
<activation><exists>some/special/path</exists></activation>
<plugins><!-- my specific configuration --></plugins></profile></profiles>

This however does not work on a per-module base in a multi-module project, but the profile is (de)activated depending on the situation on the run pom only, and this is not even documented.

In my opinion, profile activation should be on a per-module basis.

Issue Links

• duplicates: MNG-2363 <profile><activation><file><exists/> does not work in a multi-project build