This appears to be a bug that has been re-introduced into mvn 2.2.1: http://jira.codehaus.org/browse/MPH-16
I've tried it on two different maven installs using the helptest.zip file attached. On 16 September 2010 16:33, Xavier D. wrote: > I am executing a project's pom.xml directly. It has a parent "common.pom" > (common to many projects). The project is executed directly by mvn. > > Profile details were added into the pom.xml and detected automatically and > when specifying the -P <profile> on the command line. > Moving the profile details to the parent, causes the profile not to be > detected automatically or through -P usage. > > I have been testing using: mvn help:active-profiles and mvn -P > developer help:active-profiles > > Am I doing something wrong? >
