Re: [jakarta.ee-spec.committee] Jakarta EE 8 compatibility

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Scott Stark wrote on 4/18/19 10:22 AM:
> We won't support any requirement to mix the javax and jakarta
> namespaces in the runtime containers. A legacy deployment would have
> to be mapped into the new jakarta namespace.

So you want to move *everything* out of javax and into jakarta all at once?
I agree that would be best.

I sure do hope someone is working on javax.inject so that we actually *can*
move it.

> Compatibility requirements can be expressed in a canonical legacy
> deployment that is employed by the TCK to illustrate the expectations,
> but if it gets too cumbersome, it may have to be a best effort left to
> vendors.

I don't understand "illustrate the expectations".

Does that mean it's just an example?  (In which case it shouldn't be in
the TCK.)

Or do you want support for legacy deployments to be required?