[ http://jira.codehaus.org/browse/MNG-361?page=comments#action_38614 ] John Casey commented on MNG-361: --------------------------------
so we should just comment in code, and move on? That's fine, but I'd probably prefer giving the user a warning to sysout or equiv. and allowing suppression of that warning using a System property or something...for those users depending on the classes in a plugin, this will not cause a big headache, and for other cases it could make it easier to understand Maven. The vast majority will probably be in the latter case. > warn on detecting plugins in a project's dependency list > -------------------------------------------------------- > > Key: MNG-361 > URL: http://jira.codehaus.org/browse/MNG-361 > Project: m2 > Type: Bug > Components: maven-core > Versions: 2.0-alpha-1 > Reporter: John Casey > Fix For: 2.0-alpha-2 > > > Normally, plugins should not be allowed in the project's list of > dependencies. We need to examine whether this is ever a legal thing to do, > and either warn or provide an error if we detect it. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
