Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
Windows XP, Solaris x86
Maven 2.2.1
Description
In a parent pom there's a profile that's activated on the existence of a directory/file. Add that pom as the parent of a sub-module in a multi-module build; the profile activation never happens. If I build that module independently, then the profile activation works as expected.
An example project has been attached.
Attachments
Attachments
Issue Links
- duplicates
-
MNG-2363 <profile><activation><file><exists/> does not work in a multi-project build
- Closed