[jira] [Comment Edited] (MENFORCER-356) Please support m2e lifecycle management

["Robert Scholte (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MENFORCER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386339#comment-17386339 ] 

Robert Scholte edited comment on MENFORCER-356 at 7/23/21, 3:54 PM:
--------------------------------------------------------------------

I guess someone needs to apply and test https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
Based on the description I think both runOnIncremental and runOnConfiguration should be {{false}} or in other words: 

{code:xml}
      <action>
        <ignore/>
      </action>
{code}


was (Author: rfscholte):
I guess someone needs to apply and test https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
Based on the description I think both runOnIncremental and runOnConfiguration should be {{false}} or in other words: 

{format:xml}
      <action>
        <ignore/>
      </action>
{format}

> Please support m2e lifecycle management
> ---------------------------------------
>
>                 Key: MENFORCER-356
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-356
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Luke Hutchison
>            Priority: Major
>
> The maven-enforcer-plugin does not work with m2e without configuration using the `lifecyleManagement` tag. However, that tag causes numerous bad interactions between m2e and commandline mvn.
> Recently m2e added a new configuration mechanism for specifying the lifecycle management configuration:
> [https://www.eclipse.org/m2e/documentation/release-notes-17.html#new-syntax-for-specifying-lifecycle-mapping-metadata]
> The directive that works for me to get maven-enforcer-plugin to work with m2e is:
> <?m2e execute onConfiguration,onIncremental?>
> However, this style of directive, <?...?>, breaks numerous tools, including Sonatype's artifact publishing framework, and the Scrutinizer CI / static code analyzer, because they use custom XML parsers that can't yet handle this syntax. That means I have to leave the directive in the pom.xml while developing, so that I can use Eclipse, and then I have to remove it before publishing or analyzing any built jar.
> It would be very helpful if maven-enforcer-plugin could make use of the m2e lifecycle management API internally to configure itself to work with m2e, so that this directive is not needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)