The minimum compromise approach Red Hat would support would be to remove any optional TCK sets as a requirement to ratify a profile specification. Just kicking this can down the road for another release without some remediation of the current burden optional features place on the ratification process is not acceptable.
Confirming I understood correctly. You would support an approach where the CMP/BMP TCK tests are still present in the TCK, but not required for ratification. Of course any implementation that implements CMP/BMP would still be required to pass those tests.
Did I read that correctly?
-David
There is a certain "looks like a duck, walks like a duck, talks like a duck" aspect to this. If we are going to allow the majority of Platform implementations to ship CMP/BMP and users to use it, then how much work do we really want to put into this and basically get that same result?
In case this came out awkwardly, the statement being made is all proposals on the table so far still allow servers to ship CMP/BMP and users to use it, so how fancy do we want get.
-David
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
