Hi,
sounds like maven-enforcer needs a fix ?
Might it better to change maven-enforcer as well ?
Apart from Maven 3.3.4 breaking compatibility ? Or is this a good step
into future direction from Maven perspective?
Kind regards
Karl Heinz Marbaise
On 7/19/15 10:23 PM, Mirko Friedenhagen wrote:
The behaviour change was probably introduced with
https://github.com/apache/maven/commit/1d148be82bcf3e16c01477d412f4f9206445a7aa#diff-16983b0795e70151790709d0d16ab0c9R103
Before we had:
* Map<String, String> phaseToGoalMapping = null;
Now it is:
Map<String, LifecyclePhase> phaseToGoalMapping = null;
The requirePluginVersions plugin casts the entry to a string, it
probably should use String.valueOf or something.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sun, Jul 19, 2015 at 10:12 PM, Mirko Friedenhagen
<mfriedenha...@gmail.com> wrote:
This seems to affect project which use <requirePluginVersions> as an
enforcer-rule. After inserting this rule into another project I get a
similar stack trace.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
