Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] Branches and Preparing for Jakarta REST 5.0
I agree that we've been discussing this for years.   However, I believe it is required that functionality be marked as "Deprecated" with an alternative implementation for a release (point release is fine) prior to removal.   If I'm wrong on this requirement I would be fine with removing @Context in EE12.

On Fri, Oct 3, 2025 at 3:57 PM Markus KARG via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

In the end, *eventually* we need to do it some fine day, so why not in EE12? What is any better in EE13?

We're postponing this since years... 

Am 03.10.2025 um 20:27 schrieb Jim Krueger via rest-dev:
Question:  The addition of the alternative implementation for injection and the deprecation of @Context is certainly a significant change so perhaps going with 5.0 is the consensus and I'm fine with that.   But technically we could instead use a 4.1 point release for EE12 and save the full version change for the removal of @Context in EE13.     Thoughts?   We could make this change easily before the M1 release, but after that we are stuck with the full 5.0 release I think.

On Thu, Oct 2, 2025 at 4:31 AM James Perkins via rest-dev <rest-dev@xxxxxxxxxxx> wrote:
You're right. I definitely remember this now 🙂 Sorry I dropped the ball there.

This is something I can likely look at, but probably not until next week. I'm on PTO Friday and Monday, but back Tuesday.

James R. Perkins
Software Developer 

IBM
From: rest-dev <rest-dev-bounces@xxxxxxxxxxx> on behalf of Markus KARG via rest-dev <rest-dev@xxxxxxxxxxx>
Sent: Wednesday, October 1, 2025 10:08 AM
To: rest-dev@xxxxxxxxxxx <rest-dev@xxxxxxxxxxx>
Cc: Markus KARG <markus@xxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [rest-dev] Branches and Preparing for Jakarta REST 5.0
 
Welcome in the Jungle! This is exactly what I wanted to clarify many months back when I reached out to you, and the result was that nobody responded. :-( Seems we need to dive into each single commit to find out what is what. :-( -Markus Am

Welcome in the Jungle! This is exactly what I wanted to clarify many months back when I reached out to you, and the result was that nobody responded. :-(


Seems we need to dive into each single commit to find out what is what. :-(


-Markus



Am 30.09.2025 um 23:00 schrieb James Perkins via rest-dev:
Hello All,
We're aiming to have an M1 for Jakarta EE 12 by 2025-10-15 which is just a couple weeks away, see [1]. 

Looking at the branches I'm a bit confused on what branch we should be working on. There is a release-5.0 branch which is quite different from main. Both contain changes the other one does not and I don't know which one we should be using. There was a PR raised [2] to address some of the requirements for an M1 release However, some of things have already been done in the release-5.0 branch, for example removing the security manager [3].

I think the first thing we need to do is determine which branch we should use and stick with that branch. My personal preference would be main and merge what we need from release-5.0 into main, then delete the release-5.0 branch.

After that, we can start moving forward with any other changes that are needed. 



James R. Perkins
Software Developer 

IBM

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top