The difference is that the enforcer rule will prevent a build if plugin versions aren't locked down. Maven will only give warnings. My experience is that users don't care about warnings...
/Anders On Wed, Sep 8, 2010 at 20:14, Brian Fox <[email protected]> wrote: > This is coming from the enforcer rule itself, since it is coded using > bits from M2 that aren't present in M3. The workaround is to not use > this rule in M3 anymore since the core will throw warnings at you > anyway. > > On Wed, Sep 8, 2010 at 12:22 PM, Trevor Harmon <[email protected]> wrote: > > Hi, > > > > I'm trying out Maven 3.0-beta-3, and one of the first things I noticed is > a new warning message: > > > > [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-rules) @ > MyApp --- > > [WARNING] This rule is not compatible with the current version of Maven. > The rule is not able to perform any checks. > > > > The warning is caused by the presence of the following Maven Enforcer > rule: > > > > <requirePluginVersions /> > > > > I seem to remember reading somewhere that Maven 3.0 already has the > functionality of requirePluginVersions. In any case, what's the proper way > to resolve this warning? Thanks, > > > > Trevor > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
