Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Revised TCK issue section based on further discussion

...

The TCK issue mentioned in our January report for 2014 still exists.   Werner Punz summarized [1] and Leonardo Uribe[2] discussed the impacts of this issue and the impacts are summarized as follows:

  • reduces our marketability, since consumers are more likely to pick a fully-compatible open-source implementation over a partially-compatible open-source implementation.
  • reduces our compatibility with other JSF implementations, which makes it more difficult for existing JSF consumers to switch over to MyFaces.
  • reduces our compatibility with other JSF implementations, which makes it more difficult for third-party vendors to create libraries which work with all JSF implementations.
  • reduces our an open-source JSF implementation certified as
    "TCK-compliant" over a non-certified one.
  • reduces our ability to be distributed as part of a J2EE stack, like such as TomEE and Geronimo, since their TCK compliance certification depends upon our TCK compliancecertification.

[1] https://mail-search.apache.org/members/private-arch/myfaces-private/201503.mbox/%3CCAKEkEF4dF-cyXTbO=+uHBx56wnLtmezGWYUtisOw4Ffe+mtJ4A@mail.gmail.com%3E

[2] https://mail-search.apache.org/members/private-arch/myfaces-private/201503.mbox/%3CCABujnVdKyMRHh3HaN4SRGhkQzMsu9n2sK9PKiCKjgBrUpBz8AA@mail.gmail.com%3E

 

There are no new issues that require the board's attention at this time.

...