Re: [jakarta.ee-spec.committee] certification request for specs with no

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

I initially created the CR at the Interceptors spec project, but then got the feedback it could piggy back on the platform CR. 

I also assumed the former initially. Should it be decided to go for that, it's a small change to update the spec PR back to the original CR for Interceptors.

Kind regards,

Arjan

On Mon, Aug 19, 2019 at 10:11 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Some of our specs have no standalone TCK and depend on the platform
TCK for testing, such as Enterprise Beans, Managed Beans, and Interceptors.

In these cases, what do we expect for the certification request?

Should there still be a certification request filed against the corresponding
spec project, indicating that the CI is GlassFish and the TCK is the platform
TCK?

Or should the PR just reference the certification request for GlassFish for
the full platform spec?

I'm assuming the former, but it seems that some projects have done the latter,
e.g., https://github.com/eclipse-ee4j/interceptor-api/issues/49
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee