[MNG-3641] Lack of error checks on profiles

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.9
• Fix Version/s: 2.0.11, 2.1.0, 3.0-alpha-3
• Component/s: Profiles
• Flags: Patch
• Assignee: Brett Porter
• Reporter: Kohsuke Kawaguchi
• Created: 30/Jun/08 18:39
• Updated: 05/Apr/15 14:54
• Resolved: 04/Mar/09 07:22

Description

DefaultProfileManager performs no error checks on the profile IDs So If I specify bogus profile IDs from plugins (like mvn -P no-such-profile), Maven doesn't complain, and it just runs as if nothing was specified. This is very error prone.

Also, I've seen some documentation that says deactivating a profile is "-P !profile". As far as I can tell from the code, this is wrong, but because of the lack of error check, such usage just gets ignored, and the user is left confused as to why the profile isn't deactivated.

Issue Links

• is related to: MNG-4084 Unnecessary Warning for an activate profile in child project
• relates to: MNG-4583 warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds