[
https://issues.jboss.org/browse/JBIDE-9242?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9242:
------------------------------------
In this case, we should probably detect the presence of specific JSF/JSF2 classes in the
classpath, in order to add the facet.
That's what is done in m2e-wtp to handle the Web facet version. See
https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclip...
and
https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclip...
It probably needs to be refined in the case a runtime library is added to a project, all
its jars (jsf included) would be made available to the project classpath, but that
doesn't mean the project is a JSF project.
jboss-jsf-api deps on a project should trigger JSF
---------------------------------------------------
Key: JBIDE-9242
URL:
https://issues.jboss.org/browse/JBIDE-9242
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.M3
jboss-as-kickstart project in as7 quickstarts has dependency on jboss-jsf-api spec jars
but doesn't have JSF enabled.
This might be relevant for other spec jars too since the jboss ones are complete, where
as the ones in maven central are "incomplete"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira