[MNG-3017] Profile activation by file fails when maven is run outside the pom's directory

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.6
• Component/s: Profiles
• Environment: Darwin Kernel Version 8.9.1; java version "1.6.0-dp"; Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34); Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing)
• Assignee: Benjamin Bentmann
• Reporter: Jean-Luc Wasmer
• Created: 29/May/07 21:09
• Updated: 27/Mar/10 08:26
• Resolved: 27/Mar/10 08:26

Description

When calling maven outside the pom's directory, the profile activation fails:

macb:~/Development/maven-test/parent jl$ mvn install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Example parent
[INFO] Example module1
[INFO] Example module2
[INFO] ----------------------------------------------------------------------------
....

macb:~/Development/maven-test jl$ mvn -f parent/pom.xml install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Example parent
[INFO] Example module1
[INFO] ----------------------------------------------------------------------------
....

Issue Links

• duplicates: MNG-2363 <profile><activation><file><exists/> does not work in a multi-project build
• is related to: MNG-2809 Can't activate a profile by checking for the presence of a file in ${user.home}