|
Jim,
Thanks for the update.
- On 3.2: I have not seen proof that we can do 3.2 with the suggested changes (deprecations) without breaking backward compatibility. I am skeptical.
- On 3.1 for EE11: No objections.
- On 4.0 for JAXB deprecation: Seems OK at first glance.
— Santiago
On Feb 20, 2024, at 2:03 PM, Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx> wrote:
Hi,
In
this morning's EE11 Platform call there was renewed concerns about the possibility that Jakarta Rest may need to remain on 3.1 for EE11. The primary point of concern centered around the fact that XML binding would be moving to optional in EE11. This will cause
a problem for Jakarta Rest since the deprecated dependency with JAXB is not slated for removal prior to JAkarta Rest 4.0. It was discussed that we might be asked to put out Jakarta Rest 4.0 containing only the removal of the JAXB dependency. I'd also assume
if our work with release-3.2 reaches a point where it could be included in EE11 that there would likely be a push to rename 3.2 to 4.0 in order to allow the JAXB dependency removal to be included.
I
was not in a position to advocate a course of action. I felt that the group should be made aware of this discussion.
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!OKE2-3coiWbO1poF9zfNNnIeHBWQ8QGhrpflT-cPEApEZxWsoYIlXpIg0Pz5ElVotc6exqiXp5S8q5WMQ2972MSCKRgw$
|
