Hi,
On 10/10/14 4:20 PM, Michael Osipov wrote:
Hi,
On 10/10/14 3:41 PM, Paul Benedict wrote:
I would prefer this should be part of Maven Core's warning system. If the
plugin starts with maven- and it's not an org.apache.maven.plugins group,
then we should spit out the error. I am not sure enforcer is the right
place for this rule; this is more of a global problem than a suggestion for
good practice.
In my opinion this should be part of Maven Core (Maven itself within the
next version 3.2.4 ?) otherwise we can't be sure that those warnings
(possible breaks) will ever happen...
Located in the lifecycle phase of 'maven-plugin'?
No always....
We have things like dependencies / plugins without versions which
produces a warning at the moment...
this can be same ways....
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
