To start, I've searched the archives and JIRA and read through a lot of the background on this issue. For instance,
http://jira.codehaus.org/browse/MNG-2363 With that said, I'm still wondering what the current capability is for profile activation and what the future direction, if any, is planned for this feature. In my example setup, a Parent POM has a profile defined with an activation rule of <file><exists>${basedir}/somefile</exists></file> If the child project has this file, the profile is still not activated. If the parent project has this file, the profile will be activated for the parent, but not for the child. If I move the profile and activation rule to the child project, I can then run the mvn reactor on the parent and the profile will be activated for the child if the file exists. I think this last point is what mng-2363 addresses. So, with that said, I'd really like to be able to define the profiles and activation rules in a parent pom, and have the profile activation triggered within a child pom if the rules are met within the context of that child pom. Further, I don't want to have to specifiy a system property or explicit profile on the command line. Anyone know what the future direction of the profile activation is going to be? Are there any plans to change this behavior? Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
