Community Summary
-
Maven archetypes for JSF 2.2 project
We have an existing Maven archetype but we would rather someone from the community take it over and maintain it. Here is the invocation string for the 2.2 archetype:
mvn archetype:generate -DarchetypeGroupId=com.sun.faces -DarchetypeArtifactId=faces-2.2-test-war-archetype -DarchetypeVersion=0.2 -DarchetypeCatalog=https://maven.java.net/content/repositories/releases/archetype-catalog.xml
-
Help with JIRA hygiene
There are currently over 400 unresolved issues in the JIRA of record <http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC>. Surely some of them have been fixed already or are duplicates. Adding comments to the issues advising the administrators to take recommended actions would be very helpful.
-
Advocate that community driven features are driven by the community
During the JavaOne 2014 JSF BOF, we indicated that there were two drivers of features in JSF 2.3: Oracle and the community. Oracle is interested in driving features relating to platform integration, quality, and performance. The community stated interest in expanding the capabilities of JSF as suggested by EG member Ian Hlavats. These are great ideas, but perhaps if there was more pressure from the non-EG member community, we would see some progress on them in the EG.
-
Update the RealWorldJsfLinks wiki page with real world sites that use JSF
Such links are really important when trying to demonstrate the value of JSF to potential adopters.
-
serialVersionUID cleanup
We have inconsistently applied the serialVersionUID class variable to spec and impl of JSF in Mojarra. The community could really help by filing JIRAs and submitting patches against them. This is pretty much busywork, but is very necessary. This work could proceed in several phases:
Identify which classes need to be touched. Technically only those classes that will be serialized need have a serialVersionUID. With JSF, this is actually a lot of classes because of the statefulness of JSF and the support for clustering.
File JIRAs for the work. I suggest the JIRAs be filed per Java package. The Mojarra JIRA < https://java.net/jira/browse/JAVASERVERFACES > must be used here, even though there is a spec impact. Once the task gets rolling, the spec leads will file an appropriate spec JIRA. Here is the list of Java classes in the spec and Mojarra impl.
jsf-api/src/main/java/javax/faces jsf-api/src/main/java/javax/faces/application jsf-api/src/main/java/javax/faces/bean jsf-api/src/main/java/javax/faces/component jsf-api/src/main/java/javax/faces/component/behavior jsf-api/src/main/java/javax/faces/component/html jsf-api/src/main/java/javax/faces/component/visit jsf-api/src/main/java/javax/faces/context jsf-api/src/main/java/javax/faces/convert jsf-api/src/main/java/javax/faces/el jsf-api/src/main/java/javax/faces/event jsf-api/src/main/java/javax/faces/flow jsf-api/src/main/java/javax/faces/flow/builder jsf-api/src/main/java/javax/faces/lifecycle jsf-api/src/main/java/javax/faces/model jsf-api/src/main/java/javax/faces/render jsf-api/src/main/java/javax/faces/validator jsf-api/src/main/java/javax/faces/view jsf-api/src/main/java/javax/faces/view/facelets jsf-api/src/main/java/javax/faces/webapp jsf-ri/src/main/java/com/sun/faces jsf-ri/src/main/java/com/sun/faces/action jsf-ri/src/main/java/com/sun/faces/application jsf-ri/src/main/java/com/sun/faces/application/annotation jsf-ri/src/main/java/com/sun/faces/application/resource jsf-ri/src/main/java/com/sun/faces/application/view jsf-ri/src/main/java/com/sun/faces/component jsf-ri/src/main/java/com/sun/faces/component/behavior jsf-ri/src/main/java/com/sun/faces/component/validator jsf-ri/src/main/java/com/sun/faces/component/visit jsf-ri/src/main/java/com/sun/faces/config jsf-ri/src/main/java/com/sun/faces/config/configprovider jsf-ri/src/main/java/com/sun/faces/config/processor jsf-ri/src/main/java/com/sun/faces/context jsf-ri/src/main/java/com/sun/faces/context/flash jsf-ri/src/main/java/com/sun/faces/el jsf-ri/src/main/java/com/sun/faces/ext jsf-ri/src/main/java/com/sun/faces/ext/component jsf-ri/src/main/java/com/sun/faces/ext/render jsf-ri/src/main/java/com/sun/faces/ext/taglib jsf-ri/src/main/java/com/sun/faces/ext/validator jsf-ri/src/main/java/com/sun/faces/facelets jsf-ri/src/main/java/com/sun/faces/facelets/compiler jsf-ri/src/main/java/com/sun/faces/facelets/component jsf-ri/src/main/java/com/sun/faces/facelets/el jsf-ri/src/main/java/com/sun/faces/facelets/impl jsf-ri/src/main/java/com/sun/faces/facelets/tag jsf-ri/src/main/java/com/sun/faces/facelets/tag/composite jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/core jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/html jsf-ri/src/main/java/com/sun/faces/facelets/tag/jstl jsf-ri/src/main/java/com/sun/faces/facelets/tag/jstl/core jsf-ri/src/main/java/com/sun/faces/facelets/tag/jstl/fn jsf-ri/src/main/java/com/sun/faces/facelets/tag/ui jsf-ri/src/main/java/com/sun/faces/facelets/util jsf-ri/src/main/java/com/sun/faces/flow jsf-ri/src/main/java/com/sun/faces/flow/builder jsf-ri/src/main/java/com/sun/faces/io jsf-ri/src/main/java/com/sun/faces/lifecycle jsf-ri/src/main/java/com/sun/faces/mgbean jsf-ri/src/main/java/com/sun/faces/renderkit jsf-ri/src/main/java/com/sun/faces/renderkit/html_basic jsf-ri/src/main/java/com/sun/faces/scripting jsf-ri/src/main/java/com/sun/faces/scripting/groovy jsf-ri/src/main/java/com/sun/faces/spi jsf-ri/src/main/java/com/sun/faces/taglib jsf-ri/src/main/java/com/sun/faces/taglib/html_basic jsf-ri/src/main/java/com/sun/faces/taglib/jsf_core jsf-ri/src/main/java/com/sun/faces/util jsf-ri/src/main/java/com/sun/faces/util/cdi11 jsf-ri/src/main/java/com/sun/faces/vendorSubmit patches against the JIRAs. Note that IDEs provide support for generating the serialVersionUID.