[jira] [Comment Edited] (WICKET-5649) Create Eclipse lifecycle mapping for clirr-maven-plugin.

["Garret Wilson (JIRA)" <ji...@apache.org>]

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

Garret Wilson edited comment on WICKET-5649 at 8/11/14 2:11 PM:
----------------------------------------------------------------

The warning regarding no pom.xml has [Eclipse Bug 367870|https://bugs.eclipse.org/bugs/show_bug.cgi?id=367870] filed for it.

I'll admit that this whole patch is sort of a hack --- not my hack, but a hack invented by Eclipse m2e to say, "we don't have a lifecycle mapping for this particular plugin, so should we ignore it or what?"

Apparently this {{clirr-maven-plugin}} thing is obscure enough that there is no Eclipse lifecycle mapping in the Eclipse Marketplace. So the patch I provided tells Eclipse m2e to ignore it.

[~mgrigorov], the other option would be to comment out this {{clirr-maven-plugin}} altogether, as (if I remember correctly) it is disabled anyway.


was (Author: garretwilson):
The warning regarding no pom.xml has [Eclipse Bug 367870|https://bugs.eclipse.org/bugs/show_bug.cgi?id=367870] filed for it.

I'll admit that this whole patch is sort of a hack --- not my hack, but a hack invented by Eclipse m2e to say, "we don't have a lifecycle mapping for this particular plugin, so should we ignore it or what?"

Apparently this {{clirr-maven-plugin}} thing is obscure enough that there is no Eclipse lifecycle mapping in the Eclipse Marketplace. So the patch I provided tells Eclipse m2e to ignore it.

[~mgrigorov], the other option would be to comment out this {{clirr-maven-plugin}} altogether, as (if I remember correctly) it is disableld anyway.

> Create Eclipse lifecycle mapping for clirr-maven-plugin.
> --------------------------------------------------------
>
>                 Key: WICKET-5649
>                 URL: https://issues.apache.org/jira/browse/WICKET-5649
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket
>            Reporter: Garret Wilson
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 7.0.0-M3
>
>         Attachments: fix-WICKET-5649.patch
>
>
> On the 7.x development stream on {{master}}, the parent POM includes the [Clirr Maven Plugin|http://mojo.codehaus.org/clirr-maven-plugin/], although it is "Disabled until 7.0" according to the comments.
> There is no Eclipse 4.4 plugin on the marketplace for handling {{clirr-maven-plugin}}, so unless the plugin is explicitly set to be ignored or executed, Eclipse will find build errors in the project.
> The simplest approach for the time being would be to add an Eclipse lifecycle mapping to the parent POM, indicating that Eclipse should ignore the plugin (as it is disabled anyway, even in a normal Maven build outside of Eclipse).



--
This message was sent by Atlassian JIRA
(v6.2#6252)