[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Jakarta EE 8 compatibility
|
On Fri, Apr 19, 2019 at 11:12 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> 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.
>
Yes.
> > 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?
I believe this is something that will have to be explored via a
prototype legacy application deployment that is part of the TCK to
start. If there are disagreements between vendors on what can be
supported, backward compatibility may have to be a vendor specific
best effort.
