[
https://issues.apache.org/jira/browse/MENFORCER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256906#comment-17256906
]
Sylwester Lachiewicz commented on MENFORCER-351:
------------------------------------------------
Done in
[086204bc20e44989928b5106140e7247775dddb3|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=086204bc20e44989928b5106140e7247775dddb3]
> NPE when using new <?m2e execute ?> syntax with maven-enforcer-plugin
> ---------------------------------------------------------------------
>
> Key: MENFORCER-351
> URL: https://issues.apache.org/jira/browse/MENFORCER-351
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Reporter: Luke Hutchison
> Assignee: Sylwester Lachiewicz
> Priority: Major
> Fix For: 3.0.0-M4
>
>
> I get an NPE from maven-enforcer-plugin if I use the new m2e syntax that
> handles lifecycle management in Eclipse.
> I reported details here, then realized this was a maven-enforcer-plugin bug,
> not an m2e bug:
> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=560205]
> The NPE is triggered in the Maven enforcer plugin when using the m2e syntax
> along with an enforcer rule that requires a specific Maven version. See the
> above linked bug for info.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
