[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
|
Greg Wilkins wrote on 5/9/19 12:28 AM:
> ... One of my big questions about any compatibility mode is how does it change
> over time? Ie on day 1 when the behaviour of the jakarta.* version is
> identical, then a simple renaming of deployed java.* code will not produce any
> behaviour changes. However, over time, as specs evolve, the jakarta.*
> behaviours will change. Does binary compatibility mean that we map java.*
> deployments to the new behaviours (if so, that's a bigger constraint on future
> evolution of the specs), or do we maintain bug-for-bug behaviours for javax.*
> deployments?
The same issue would occur if we didn't have to change the package name. Even
if we were still using javax.* and evolving the APIs over time, would
applications written for Jakarta EE 9 continue to run without change on Jakarta
EE 12?
That sort of version-to-version compatibility was always a goal of Java, and
while it wasn't achieved perfectly, I think we did a pretty good job. But many
people have recognized the cost of providing that level of compatibility, and
even Java SE now has a process for removing APIs and thus breaking compatibility.
We need to decide what our level of commitment to version-to-version
compatibility is for Jakarta EE, and that's largely independent of the javax.*
issue.
