<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
So we don't have to care about maven builder order.<br>
Thanks Fred.<br>
<br>
On 07/25/2011 01:01 AM, Fred Bricon wrote:
<blockquote cite="mid:4E2D22E8.2070706@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi Alexey,<br>
<br>
see Igor's reply :<br>
<br>
<div class="gmail_quote">
<blockquote>---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Igor Fedorenko</b> <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:igor@ifedorenko.com">igor@ifedorenko.com</a>></span><br>
Date: 2011/7/25<br>
Subject: Re: [m2e-dev] Questions about the Maven Builder<br>
To: <a moz-do-not-send="true"
href="mailto:m2e-dev@eclipse.org">m2e-dev@eclipse.org</a><br>
<br>
<br>
In theory, builders order should not matter. Builders produce
workspace<br>
changes, so if m2e builder changed any workspace resources,
this will<br>
trigger new build cycle (assuming workspace build is ON, of
course), and<br>
these changes will be picked up by other builders.<br>
<br>
Project metadata changes is another story. Although I have not
seen this<br>
is documented anywhere, I believe general assumption is that
project<br>
configuration is (relatively) static and does not change as a
result of<br>
project build. So if maven builder changes or updates project<br>
configuration (things like application.xml and OSGi bundle
manifest), it<br>
sort of falls into a gray territory, in theory everything is
supposed to<br>
work, but in practice some tools may get confused and may need
extra<br>
help to "notice" new project metadata.<br>
<br>
--<br>
Regards,<br>
Igor</blockquote>
<div class="im"><br>
m2e configurators (JDT, WTP, JSF, CDI ...) are all called by
the maven builder, hence the phrase "if m2e builder changed
any workspace resources ...". As a matter of fact, resources
are being created/changed by these configurators, generating
new build cycles. HIH.<br>
<br>
Regards,<br>
<br>
Fred Bricon<br>
<br>
<br>
<br>
On 11-07-25 12:00 AM, Fred Bricon wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="im"> Hello World,<br>
<br>
I'm not sure about the answer so I think it's best if I
forward the<br>
question here :<br>
<br>
-------- Original Message --------<br>
Subject: Maven builder<br>
Date: Fri, 22 Jul 2011 16:30:55 -0700<br>
</div>
From: Alexey Kazakov <<a moz-do-not-send="true"
href="mailto:akazakov@exadel.com" target="_blank">akazakov@exadel.com</a>
<mailto:<a moz-do-not-send="true"
href="mailto:akazakov@exadel.com" target="_blank">akazakov@exadel.com</a>>><br>
Reply-To: <a moz-do-not-send="true"
href="mailto:akazakov@exadel.com" target="_blank">akazakov@exadel.com</a>
<mailto:<a moz-do-not-send="true"
href="mailto:akazakov@exadel.com" target="_blank">akazakov@exadel.com</a>><br>
To: <a moz-do-not-send="true"
href="mailto:fbricon@redhat.com" target="_blank">fbricon@redhat.com</a>
<mailto:<a moz-do-not-send="true"
href="mailto:fbricon@redhat.com" target="_blank">fbricon@redhat.com</a>>,
jbosstools-dev
<div class="im"><br>
<<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
</div>
<mailto:<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a>>>
<div class="im"><br>
<br>
<br>
<br>
Hi Fred,<br>
<br>
Fighting with Jose Freitas' problem with not-working code
completion<br>
for JSF tags I looked at his .project file: <a
moz-do-not-send="true" href="http://pastebin.com/bDLDDq2C"
target="_blank">http://pastebin.com/bDLDDq2C</a><br>
There is a builder org.eclipse.m2e.core.maven2Builder
which<br>
</div>
isdeclared as the last one in the list of the builders.
Eventually
<div class="im"><br>
we found the reason of not-working code completion. It's
not related<br>
to maven stuff at all (he didn't install JSF tools:<br>
<a moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBIDE-9397"
target="_blank">https://issues.jboss.org/browse/JBIDE-9397</a>
). But anyway, could it<br>
be a problem if the maven builder declared last? For
instance:<br>
<br>
1. Java builder build the project.<br>
2. CDI builder builds the project using Java model (cdi
builder<br>
should be declared after Java builder and we create a
problem marker<br>
if it's not so).<br>
3. KB builder builds the project using Java model (so we
check the<br>
build order again).<br>
4. WST validation builder validate the project. We extend
this<br>
validation and check if CDI, KB, Seam builders declared
before the<br>
WST builder.<br>
<br>
So, what about Maven? Does it do anything that could
influence CDI,<br>
JSF, Seam and don't trigger a new cycle of building?
Should we care<br>
if maven declared after CDI/KB/WST?<br>
I tested Jose's project and everything seems to work, but
I could<br>
miss something.<br>
<br>
<br>
<br>
Thanks for you insights.<br>
<br>
Regards,<br>
<br>
Fred Bricon<br>
--<br>
"Have you tried turning it off and on again" - The IT Crowd<br>
<br>
<br>
</div>
_______________________________________________<br>
m2e-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:m2e-dev@eclipse.org"
target="_blank">m2e-dev@eclipse.org</a><br>
<a moz-do-not-send="true"
href="https://dev.eclipse.org/mailman/listinfo/m2e-dev"
target="_blank">https://dev.eclipse.org/mailman/listinfo/m2e-dev</a><br>
</blockquote>
_______________________________________________<br>
m2e-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:m2e-dev@eclipse.org"
target="_blank">m2e-dev@eclipse.org</a><br>
<a moz-do-not-send="true"
href="https://dev.eclipse.org/mailman/listinfo/m2e-dev"
target="_blank">https://dev.eclipse.org/mailman/listinfo/m2e-dev</a><br>
</div>
<br>
<br clear="all">
<br>
-- <br>
"Have you tried turning it off and on again" - The IT Crowd<br>
<br>
</blockquote>
<br>
</body>
</html>