WFLY-1880 Update JSF based on Mojarra 2.2.2

[ssilvert]

No description provided.

[wildfly-ci]

Build 453 is now running using a merge of dd646d5

[wildfly-ci]

Build 453 outcome was FAILURE using a merge of dd646d5
Summary: Tests passed: 1829, ignored: 12; exit code 1 (new) Build time: 0:9:58

[ssilvert]

Retest this please.

[wildfly-ci]

Build 454 is now running using a merge of dd646d5

[wildfly-ci]

Build 454 outcome was FAILURE using a merge of dd646d5
Summary: Tests passed: 1829, ignored: 12; exit code 1 Build time: 0:8:18

[kabir]

Step 2/3: Build & test (Maven) (8m:11s)
[13:18:09][Step 2/3] org.wildfly:wildfly-jsf (5s)
[13:18:15][org.wildfly:wildfly-jsf] Failed to execute goal on project wildfly-jsf: Could not resolve dependencies for project org.wildfly:wildfly-jsf:jar:8.0.0.Beta1-SNAPSHOT: Could not find artifact org.jboss.spec.javax.faces:jboss-jsf-api_2.2_spec:jar:2.2.2 in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/)
[13:18:20][Step 2/3] Step Build & test (Maven) failed

[ssilvert]

This is really odd. I deployed the API and Impl to Nexus at the same time the same way I always do. The Impl was deployed correctly but the API got deployed to the JBoss Thirdparty repo. I have no idea how that could happen or how to fix it.

[jaikiran]

I have no idea how that could happen or how to fix it.

These days it requires dropping a mail to jboss.org team. I'll send you the mail id to use, in private.

[wildfly-ci]

Build 210 is now running using a merge of dd646d5

[wildfly-ci]

Build 210 outcome was SUCCESS using a merge of dd646d5
Summary: Tests passed: 4397, ignored: 84 Build time: 1:5:2

[bstansberry]

Merged.