Upgrade JSF test to use MyFaces 2.2.x [PAXWEB-732]

[ops4j-issues]

Achim Nierbeck created PAXWEB-732

This will be hard to achieve for 4.1.0 since MyFaces explicitly requires Servlet API in range [2.5,3.1), so this won't work on Version 4.1

---

Affects: 4.0.0 Fixed in: 4.0.1, 4.1.0 Votes: 0, Watches: 1

[ops4j-issues]

Achim Nierbeck commented

Branch: refs/heads/pax-web-4.0.x
Home: https://github.com/ops4j/org.ops4j.pax.web
Commit: b697a8ce91cf1e938d00d35c745ec8801cdb743a
https://github.com/ops4j/org.ops4j.pax.web/commit/b697a8ce91cf1e938d00d35c745ec8801cdb743a
Date: 2014-09-12 (Fri, 12 Sep 2014)

---

Branch: refs/heads/pax-web-3.1.x
Home: https://github.com/ops4j/org.ops4j.pax.web
Commit: 2cf07a25c5c9cdb4ea567f9662aa1c2cc290ffc1
https://github.com/ops4j/org.ops4j.pax.web/commit/2cf07a25c5c9cdb4ea567f9662aa1c2cc290ffc1
Date: 2014-09-12 (Fri, 12 Sep 2014)

[ops4j-issues]

Achim Nierbeck commented

The commit to 3.1.x breaks the itests on that branch
PAXWEB-733 , will take care of this.

[ops4j-issues]

Achim Nierbeck commented

Pax Web 3.x is not compatible with MyFaces 2.2.x, it needs to be rolled back.

[ops4j-issues]

Achim Nierbeck commented

roled back for 3.1.x:

Branch: refs/heads/pax-web-3.1.x
Home: https://github.com/ops4j/org.ops4j.pax.web
Commit: 9b44ee0ba5e0746733c57c1ca6a6ed097a24440f
https://github.com/ops4j/org.ops4j.pax.web/commit/9b44ee0ba5e0746733c57c1ca6a6ed097a24440f
Date: 2014-09-27 (Sat, 27 Sep 2014)

[ops4j-issues]

Achim Nierbeck commented

fails again, with Context is already initialized ....

[ops4j-issues]

Achim Nierbeck commented

finally fixed on 4.1.0:
—
https://github.com/ops4j/org.ops4j.pax.web/commit/6338df3f71e0ce4b5338c8664cee47ff86c843b0

4.0.1:
still missing

[ops4j-issues]

Achim Nierbeck commented

fat-finger syndrome today ...
fix for 4.0.x is missing ..

[ops4j-issues]

Achim Nierbeck commented

resolved for 4.0.1 too