[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_50257 ]
John Casey commented on MNG-1388:
-
This happens because dependency POMs aren't currently candidates for profile
triggering.
However, it seems we will have to trigger profiles for these
[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_50042 ]
Damian Bradicich commented on MNG-1388:
---
Here is an example of 2 pom files that will show the problem, also note that
the active profile is defined in settings.xml
project