[
https://issues.jboss.org/browse/WFLY-9836?page=com.atlassian.jira.plugin....
]
Ivo Studensky commented on WFLY-9836:
-------------------------------------
Farah's comment:
{quote}
I was just taking a look at the current jboss-jsf-api_spec version (2.2.14) in the WildFly
pom.xml file and realized that this version is actually wrong. It was recently updated in
a mass update to spec versions from 2.2.13 to 2.2.14 by \[1\] even though the only change
made in the jboss-jsf-api_spec repo was in the pom.xml file, i.e., the JSF API bits
weren't updated at all and still correspond to the Mojarra 2.2.13 API version. Thus,
this version should really have been named 2.2.13.SP1, not 2.2.14. I've now made the
following changes:
i) I've applied the jboss-jsf-api_spec pom.xml file changes that went into the
erroneous 2.2.14 version to the 2.2.13.SP branch and I've created a 2.2.13.SP1 release
containing these changes.
ii) I've applied the PR for WFLY-9838 to the 2.2.13.SP branch and I've created a
2.2.13.SP2 release containing these changes. The tag can be found here:
https://github.com/jboss/jboss-jsf-api_spec/commits/jboss-jsf-api_2.2_spe...
\[1\]
https://github.com/wildfly/wildfly/commit/1d8f7fef021f7af9e764bbe0ef1cedc...
{quote}
Upgrade jboss-jsf-api_spec to 2.2.13.SP2
----------------------------------------
Key: WFLY-9836
URL:
https://issues.jboss.org/browse/WFLY-9836
Project: WildFly
Issue Type: Component Upgrade
Components: JSF
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Upgrade of jboss-jsf-api_spec (jboss.spec.javax.faces.jboss-jsf-api_2.2_spec) to fix
WFLY-9838.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)