JSF 2.3 only came out very recently, and I'm having problems getting it to work with Eclipse. I have earlier versions of JSF installed correctly, and in Eclipse when I go to Dynamic Web Project [Project name] and select for Target runtime Glassfish, and select for also Glassfish for configuration, then click on Modify... a new window opens with various versions of Java, JavaServer Faces, etc. Java 1.8 is selected by default, which I want, but Java Server Faces only has selections for 2.2 and earlier versions, and I'm unable to get 2.3 shown as being available, so what do I do?
I downloaded javax.faces-2.3.0.jar from https://maven.java.net/content/repositories/releases/org/glassfish/javax.faces/2.3.0/, then on my Windows computer found that in the Eclipse workspace I have the folder JSF 2.2 (Mojarra 2.2.0)\mojarra-2.2.0-FCS\lib\javax.faces.jar, so I created a new lib folder with the same path as above, except the I replaced 2.2 by 2.3 in all cases, copied the jar file into the new lib folder, then renamed it javax.faces.jar.
After closing then restarting Eclipse, I'm unable to select any version of JSF higher than 2.2. I can link the jar file directly into the project and it works, but Eclipse will not recognize the h: and f: tags in the XHTML source code, so obviously JSF is not linked properly with Eclipse, and would most appreciate some advice on fixing this.
This has all been done with Eclipse Mars.2 Release (4.5.2). I've now just installed Eclipse Neon and I'm still unable to get JSF 2.3 when I try to create a Dynamic Web Project. In fact in the Neon workspace there is no libraries folder, and because I have not yet successfully created any projects, there are also no project folders.
How do I get Eclipse to recognize JSF 2.3, and will the next version of Eclipse, Oxygen, which is due to come out in June this year, have JSF 2.3 automatically included?
I'm afraid that I tend to use Eclipse as a fairly blunt instrument. Thanks to lack of proper training and bugs in various versions of Eclipse, my webapps are plain Java projects. About the only facet that I regularly map to them is Maven.
I'm afraid I have a poor opinion of overly-helpful IDEs anyway. I got burned really badly on Microsoft Visual Studio many years ago, and these days I use an IDE to develop and test, but my production builds are all expected to work far away from a GUI or an IDE. Typically via Maven or Ant, either stand-alone or driven by Jenkins.
In particular, I've had bad experiences with the Enterprise Java plugins on the J2EE spins of Eclipse. A most notable example is that the Tomcat plugins do horrible things to the Tomcat runtime environment, so I've found it better to install the sysdeo/mongrel plugin and ignore the built-in Tomcat services.
The downside of this is that I don't get as much help from the IDE when developing. The upside is that I'm not as dependent of specific versions of the runtimes. I can deal with 2 or more different versions of JSF, for example, since I reference libraries symbolically in the project properties instead of being beholden to whatever version(s) the IDE is presently wired to accept.
An IDE is no substitute for an Intelligent Developer.