Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Incremental vs Big Bang thought experiment

It's all or nothing.  Anything that remains in javax has to meet the existing spec requirements, which would be impossible to meet if some of the APIs were missing because they were moved to jakarta.*.

Scott Stark wrote on 5/29/19 11:49 AM:
I’m going through a little exercise to help clarify where an incremental vs Big Bang approach might differ in terms of compatibility requirements as well as general effort. The context of the experiment is to update the enterprise security api to factor out the servlet specific and jsr-196 apis into a new package so that the HttpAuthenticationMechanism
Interface  or a variation of it could be used without those dependencies.

First question that comes to mind, under the incremental approach, would a change to the spec that only affects a subset of the javax.security.enterprise.* packages leave some packages under javax.security.enterprise.* and the changed classes under jakarta.security.enterprise.*, or when a spec is updated would all associated package be moved over to jakarta.*?


_______________________________________________
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


Back to the top