Closed scottmarlow closed 1 week ago
This is certainly related to #133 because the assumption to date is that the generated test class is just a trigger to invoke the test through the javatest/appclient protocols. These really only need the legacy base test class to work. If we have generated tests that have logic to execute, then we need to both use the generated test class as the server side target and include it in the deployment artifiact. The only question I have is how to detect the different requirement.
Just to confirm that I am no longer using the hack of adding class ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest.class
which I mentioned in the description. I closed #133 and will close this issue as well as they are no longer a problem.
Locally, I hacked the following change:
Can tck-rewrite-ant add the
ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest.class
class? Or do we need a change elsewhere?