<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I have never encountered that plugin before, looks like John wrote it, so if I say something stupid he can correct me.</div><div class=""><br class=""></div><div class="">m2e doesn’t know whether it’s safe to execute or to ignore that plugin in the context of an Eclipse build.</div><div class="">Quickly looking at [1], I would say assembling the project sources is irrelevant to building an app and deploy it *from Eclipse*. So I would say it’s safe to ignore it. But that really depends on the project. I don’t know if it _needs_ it’s sources to be deployed at runtime.</div><div class=""><br class=""></div><div class="">If it’s actually safe to ignore, you have 3 options :</div><div class="">- mark as ignore in pom.xml : you need to do that in each and every quickstart project, but you guarantee your users won’t see an error on import</div><div class="">- mark as ignore in Eclipse : you need to do that once per workspace, but this has to be a user action. You can only document that step in each quickstart</div><div class="">- ask John to add a META-INF/m2e/lifecycle-mapping-metadata.xml file in his plugin [2], so that m2e will safely ignore it by default, with any further pom.xml meddling</div><div class=""><br class=""></div><div class="">As a general rule, I would say that yes, you should try to avoid using non-standard, unsupported maven plugins in Eclipse. You’ll run into less trouble.</div><div class="">If you can’t avoid it, then adding the lifecycle-mapping in the pom (provided it’s safe) will guarantee your users won’t see any errors.</div><div class=""><br class=""></div><div class="">Fred</div><div class=""> </div><div class="">[1] <a href="https://github.com/jdcasey/project-sources-maven-plugin/blob/master/src/main/java/org/commonjava/maven/plugins/projectsrc/ProjectSourcesGoal.java" class="">https://github.com/jdcasey/project-sources-maven-plugin/blob/master/src/main/java/org/commonjava/maven/plugins/projectsrc/ProjectSourcesGoal.java</a> </div><div class="">[2] <a href="https://wiki.eclipse.org/M2E_compatible_maven_plugins#Overview" class="">https://wiki.eclipse.org/M2E_compatible_maven_plugins#Overview</a></div><br class=""><div><blockquote type="cite" class=""><div class="">Le 4 juin 2015 à 11:09, Sande Gilda <<a href="mailto:sgilda@redhat.com" class="">sgilda@redhat.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
Fred, did we run into this issue with any of the JBoss EAP
quickstarts? It sounds familiar, but I can't find anything.<br class="">
<br class="">
<div class="moz-cite-prefix">On 06/04/2015 09:10 AM, Rafael
Benevides wrote:<br class="">
</div>
<blockquote cite="mid:55704E53.7080408@redhat.com" type="cite" class="">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252" class="">
Hi all,<br class="">
<br class="">
Recently I reported a bug to BRMS Quickstarts where it couldn't be
built when imported to JBDS due to the existence of a maven plugin
not covered by m2e.<br class="">
<br class="">
When the Quickstart gets imported, it says:
<meta charset="utf-8" class="">
"Plugin execution not covered by lifecycle configuration:
org.commonjava.maven.plugins:project-sources-maven-plugin:0.3:archive
(execution: project-sources-archive, phase: initialize)"<br class="">
<br class="">
The question is: What's the recommendation from JBDS guys for
this?<br class="">
<br class="">
1 - Avoid non-convered plugins by m2e<br class="">
2 - Mark it as ignored in the pom.xml when importing it<br class="">
3 - Mark it as as ignored in eclipse (experimental)<br class="">
4 - Other recommendation<br class="">
<br class="">
<br class="">
For reference, the related bug is <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1227861">https://bugzilla.redhat.com/show_bug.cgi?id=1227861</a><br class="">
<br class="">
<div class="moz-signature">-- <br class="">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252" class="">
<div style="font-family: Arial; font-size: 10pt;" class=""><br class="">
<b class="">Rafael Benevides | Senior Software Engineer</b><br class="">
JBoss Developer Materials lead<br class="">
M: +1-919-592-6255<br class="">
<br class="">
<span id="cid:part2.09060800.02060202@redhat.com"><Pièce jointe.jpeg></span><br class="">
<br class="">
Better technology. Faster innovation. Powered by community
collaboration. <br class="">
See how it works at <a moz-do-not-send="true" href="http://www.redhat.com/" class="">www.redhat.com</a> <br class="">
<br class="">
<a moz-do-not-send="true" href="http://www.linkedin.com/company/3258288" class=""><span id="cid:part4.00080804.05030508@redhat.com"><Pièce jointe.png></span></a> <a moz-do-not-send="true" href="https://www.youtube.com/redhatlatam" class=""><span id="cid:part6.05060009.04030902@redhat.com"><Pièce jointe.png></span></a> </div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
jbossdeveloper mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a></pre>
</blockquote>
<br class="">
</div>
</div></blockquote></div><br class=""></body></html>