Re: [jakartaee-tck-dev] How to treat TCK test code for pruned technologi

[Lance Andersen <lance.andersen@xxxxxxxxxx>]

Hi Scott,

If the API has been completely removed, the code should be removed.  If the technology is optional, then the code should remain and configurable for testing similar to what is done for the Web Profile

Best

Lance

On Apr 2, 2020, at 12:00 PM, Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

[1] is commenting out a call to SessionContext#getMessageContext() as JAX-RPC is on the list to be pruned for Jakarta EE 9.  We added a "TODO: verify" comment, do we need to do anything else?  Should the (pruned technology) test code be deleted instead, since it cannot possibly work anymore?  

Scott

[1] https://github.com/eclipse-ee4j/jakartaee-tck/pull/186/files#r402422902

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering 
1 Network Drive 
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx