[ http://jira.codehaus.org/browse/MNG-361?page=all ]
Brett Porter updated MNG-361:
-----------------------------
Fix Version: (was: 2.0-alpha-3)
2.0-alpha-2
as far as it acting as a plugin - definitely not. So if that were the only
case, then I'd be all for banning types maven-plugin as a dependency.
But I can think of other use cases:
- adding a plugin to the classpath, so your mojos can be reused. I don't know
if we want to encourage that, but I imagine there is probably a valid use case
- aggregating for distribution.
So I think we should allow it, and just document that it doesn't do anything
WRT the build process.
Do you agree?
> 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]
