[
https://issues.jboss.org/browse/JBIDE-10468?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-10468.
---------------------------------
Resolution: Done
Fixed in trunk. faces-config.xml is first searched for and analyzed for the JSF version,
then we fallback on analyzing the JSF dependencies in classpath,
then we check if web.xml contains javax.faces.webapp.FacesServlet.
In that case, if the Web Facet is >= 3.0, we assume JSF 2.0, or 1.2 otherwise.
jsf enablement should not just look for dependency but also be
enabled if /WEB-INF/faces-config.xml is there
------------------------------------------------------------------------------------------------------------
Key: JBIDE-10468
URL:
https://issues.jboss.org/browse/JBIDE-10468
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Blocker
Fix For: 3.3.0.Beta1
From Pete Muir:
"JSF is included - there is a src/main/webapp/WEB-INF/faces-config.xml to activate
JSF on JBoss AS 7. There is no compile time dependency, as most people start with JSF
simply through the XHTML markup, and only when they need to do something advanced,
actually start using the JSF Java API. I would suggest you trigger the JSF facet based on
the presence of the above file or the web.xml stanza, not based on the POM. This is the
way an app server does it, so you will see most fidelity this way."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira