<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Fred,<br>
<br>
Fighting with Jose Freitas' problem with not-working code completion
for JSF tags I looked at his .project file: <a
href="http://pastebin.com/bDLDDq2C">http://pastebin.com/bDLDDq2C</a><br>
There is a builder org.eclipse.m2e.core.maven2Builder which is<span
class="Apple-style-span" style="color: rgb(0, 0, 0); font-family:
arial,sans-serif; font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal;
line-height: 18px; orphans: 2; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
background-color: rgb(255, 255, 255);"></span> declared as the
last one in the list of the builders. Eventually we found the reason
of not-working code completion. It's not related to maven stuff at
all (he didn't install JSF tools: <a
href="https://issues.jboss.org/browse/JBIDE-9397">https://issues.jboss.org/browse/JBIDE-9397</a>
). But anyway, could it 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
should be declared after Java builder and we create a problem marker
if it's not so).<br>
3. KB builder builds the project using Java model (so we check the
build order again).<br>
4. WST validation builder validate the project. We extend this
validation and check if CDI, KB, Seam builders declared before the
WST builder.<br>
<br>
So, what about Maven? Does it do anything that could influence CDI,
JSF, Seam and don't trigger a new cycle of building? Should we care
if maven declared after CDI/KB/WST?<br>
I tested Jose's project and everything seems to work, but I could
miss something.<br>
<br>
</body>
</html>