[ http://jira.codehaus.org/browse/MNG-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3641: ----------------------------------- Fix Version/s: 3.0-alpha-3 Ported to 3.x in [r787045|http://svn.apache.org/viewvc?view=rev&revision=787045]. > Lack of error checks on profiles > -------------------------------- > > Key: MNG-3641 > URL: http://jira.codehaus.org/browse/MNG-3641 > Project: Maven 2 > Issue Type: Bug > Components: Profiles > Affects Versions: 2.0.9 > Reporter: Kohsuke Kawaguchi > Assignee: Brett Porter > Fix For: 2.0.11, 2.1.0, 3.0-alpha-3 > > Attachments: MNG-3641-IT.tar.gz, MNG-3641-maven-project.patch, > mng-3641.zip > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira