| [glassfish-dev] Thoughts on the current GlassFish porting implementation classes/deployment descriptors that are in the Platform TCK |
Hi,
Where will the GlassFish team maintain the GlassFish TCK porting
kit implementation [1]? Perhaps the GlassFish TCK porting kit
should be moved
Currently, it is part of the Platform TCK which means that the
GlassFish project is pretty much tied to the Platform TCK for
making TCK porting kit changes. There are also a lot of GlassFish
deployment descriptors [2] in the Platform TCK as well.
The GlassFish Porting kit TCK [1][2] files can currently be used by any Jakarta EE implementation (I know that WildFly currently uses some of these files and I think others do as well). The Platform TCK still mentions that any EE implementation may depend on the GlassFish TCK porting kit in various places [3].
Should files like [1][2][3] be copied to a
glassfish-platform-porting-tck repo similar to [4]?
Scott
[1]
https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/src/com/sun/ts/lib/implementation/sun
[2]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/jta/ee/usertransaction/settransactiontimeout/settransactiontimeout_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
[3]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/lib/implementation/sun/common/SunRIURL.java#L24
[4] https://github.com/eclipse-ee4j/glassfish-cdi-porting-tck