The fact that a profile is activated from the command line or settings.xml applies to the entire execution, which means if that profile is exists in multiple modules, it will be activated in each of them. The original issue for this was: http://jira.codehaus.org/browse/MNG-1420
-----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Sunday, April 27, 2008 8:13 PM To: Maven Developers List Subject: Re: Multiple -P options On Mon, Apr 28, 2008 at 9:17 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I tried fixing that before and it caused a ton of issues. Not every > project will contain the profile to be activated so it warns/errors on > all of them that don't...this is even more of a mess. Profiles are only meant to be activated at the same directory that mvn is run. They don't get passed on down to modules. (I've had problems with this misunderstanding before) So why should there be lots of warnings? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
