[MNG-2363] <profile><activation><file><exists/> does not work in a multi-project build

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.0-alpha-3
• Component/s: Profiles
• Assignee: Benjamin Bentmann
• Reporter: David Boden
• Created: 12/Jun/06 12:31
• Updated: 23/Mar/14 12:36
• Resolved: 25/Jun/09 07:04

Description

I would expect each subproject to have the profile turned on or off depending on whether ${basedir}/file-to-check-for exists.

Instead, during a multi-project build the profile is either on or off depending on whether the file exists relative to the aggregator pom. The decision is made once.

Variable substitution doesn't work, so I can't explicitly use <exists>${basedir}/file-to-check-for</exists> or any variation on this theme to workaround the bug.

Some background to my particular problem. I have 10 modules to build. Some of them are GUI modules and contain a file called plugin.xml in the subproject directory. I want to package these up specially and sign them, ready for deployment to webstart. The other modules are shared and server code and I don't want these packaged in the same way. So, I've got a dependency in my parent pom file which activates a profile called "guibundle" if a plugin.xml file exists in the subproject directory.

Issue Links

• is duplicated by: MNG-1775 No property expansion in profile activation
• is duplicated by: MNG-3017 Profile activation by file fails when maven is run outside the pom's directory
• is duplicated by: MNG-3524 Profile to be activated when file is missing is always activated
• is duplicated by: MNG-4120 Profile activation should be per module
• is duplicated by: MNG-4174 Inheritance from profiles from parent-pom to child-pom
• is duplicated by: MNG-4620 Reporting profiles not executed in child modules.
• is duplicated by: MNG-3140 add support for ${basedir} property in profile activation
• is related to: MNG-5608 warn if file-based profile activation uses ${project.basedir} since only ${basedir} is supported
• relates to: MNG-4735 File-based profile activation behaves differently in Maven 3
• relates to: MNG-5360 profile/activation/file does not work with ${project.basedir}, only with ${basedir}