[
https://issues.apache.org/jira/browse/WICKET-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092782#comment-14092782
]
Martin Grigorov commented on WICKET-5649:
-----------------------------------------
No. I don't use Eclipse.
But no one else wants to do it ... :-/
For me this m2e thingy gives errors in Intellij IDEA (colored in red) and
warnings in Maven command line execution (says there is no pom.xml for it at
Maven Central).
But I don't mind them if this will make other developers happier.
> 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)
