| Re: [jaxrs-dev] [External] : Avoiding `jakarta` prefix in TCK tests + pr#1082 |
_______________________________________________
https://github.com/eclipse-ee4j/jaxrs-api/pull/1082 is just a draft. It should be a regular PR before it gets merged.
But I am +1 to have something like that for EE 10, where it has been migrated from the TCK repo. Renaming it after EE 10 will probably cause a loss of history (or at least it won't be easily visibly in git blame) which likely is not what we want.
-- Jan
From: jaxrs-dev <jaxrs-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx>
Sent: Tuesday, January 18, 2022 7:23 PM
To: jaxrs developer discussions <jaxrs-dev@xxxxxxxxxxx>
Subject: [External] : [jaxrs-dev] Avoiding `jakarta` prefix in TCK tests + pr#1082One new namespace requirement for TCKs is being discussed in both the Jakarta Platform + SPEC calls/ml discussions. The current concern mentioned in [1] is for TCK test deployment classes that start with the "jakarta" namespace prefix. The concern is that some implementations may later challenge such TCK tests due to the "jakarta" package prefix being used.
[2] is a pull request that is intended to update the Jakarta REST TCK tests to not use the "jakarta" namespace. Would it be possible to merge [2] or a change like that for REST 3.1?
Scott
[1] https://docs.google.com/document/d/1DF0T2hbJqDNsY0v_lYFKCz-ZgHPbnMUIu6mhmt5LCJU/edit?pli=1# (see "Concern about future TCK challenges due to use of `jakarta` in test packages")
[2] https://github.com/eclipse-ee4j/jaxrs-api/pull/1082
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev