You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2020/12/31 09:07:00 UTC

[jira] [Assigned] (MENFORCER-351) NPE when using new syntax with maven-enforcer-plugin

     [ https://issues.apache.org/jira/browse/MENFORCER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz reassigned MENFORCER-351:
----------------------------------------------

    Assignee: Sylwester Lachiewicz

> 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
>
> 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)