| [jakartaee-tck-dev] EE 10 + brainstorming on what to do with the TCK Porting kit interfaces like TSURLInterface... |
Issue 737 [1] is for eliminating the Platform TCK interfaces [2]
or replacing them with a different mechanism that doesn't require
the Platform TCK porting kit interfaces [2]. The JAX-RS 3.1 TCK
proof of concept effort [3] is currently including its own copy of
the TSURLInterface interface (+ SunRIURL [4]) .
If we do need to publish a common Platform TCK Porting kit artifact, that would need to go through its own release ballot so we need to identify if we really need to accomplish that or if its better to eliminate the Platform TCK porting interfaces.
One idea is to publish extensible TCK porting implementation
classes that EE implementations could override via system
properties defined on the maven command line.
Other suggestions?
Scott[1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/737
[2]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/lib/porting
[3]
https://github.com/eclipse-ee4j/jaxrs-api/pull/1002#issuecomment-906644933
[4]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/lib/implementation/sun/common/SunRIURL.java