FYI, I'm in a conversation with Java EE leads and TCK team about this. It seems we may be able to re-apply this particular change.
Marek
On Jan 17, 2013, at 11:38 PM, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
> Hi
>
> Comment from Marek at
>
> http://java.net/jira/browse/JAX_RS_SPEC-326
>
> got me actually concerned, though may be it is unfounded - apologies if so.
>
> Basically I do not get why the change to do with JAX-RS 1.1 TCK signature tests was made after JAX-RS 2.0 m10, in fact, different people run TCK 1.1 against CXF JAX-RS 1.1 implementation and it passed, thus I'm worried about this change ?
> Also - should the actual TCK be 'challenged' and the issue be fixed there instead of pushing it to the API level ?
>
> Looking forward to some comments
> Thanks, Sergey