| Re: [jakarta.ee-community] [jakarta.ee-spec] Defining Jakarta EE 12 Scope in Program Plan |
Hi Scott,
If you take a look at the long-standing items in the Jakarta EE Ambassadors' Contributor Guide (https://jakartaee-ambassadors.io/guide-to-contributing-to-jakarta-ee-11/), the following items are along these lines:
* Modernizing the TCK to take advantage of Maven, JUnit, Arquillian, etc. It has long been well understood that not doing this work reduces the velocity of releases of the platform and older specifications. It also makes the TCK inaccessible to new contributors. My understanding from Ed is that this is well on the way to being resolved now. That's why I did not include it in the Jakarta EE 12 potential plan. Is that not the case? Also, unfortunately most users and customers would not really care about this, so it has to be balanced with more marketable changes.
* Making specification TCKs standalone as much as possible and
making more specifications usable on their own in plain Java SE,
without a Jakarta EE runtime. This should include bootstrap APIs
for things like Messaging and Servlet. Indeed this could include a
Java SE bootstrap API for Jakarta EE itself. If there is appetite
for it, consensus around it, and we take it seriously to get it
really done, this could be a very nice marketable item for Jakarta
EE 12. The reason I did not include it is because I assess this to
be an even steeper effort as compared with what I already included
that could make EE 12 get some real market attention.
* Improving testing for Jakarta EE. This could take several forms. It could simply mean accepting that Arquillian is the de-facto answer and making sure it is as good as it can be (and I think currently it is not). It could be moving Arquillian to the Foundation and improving it there (would Red Hat be open to this?). It could mean basically standardizing the Arquillian API into Jakarta EE. It could also mean taking a fresh look at standardizing a testing API by looking at things like Testcontainers. Any of these could be pretty marketable for Jakarta EE 12. The reason I did not include it is that in my assessment this will take an even longer time to figure out than what I already listed.
Is any/some of these things what you had in mind or are you
thinking of something else we had not already identified for a
while as a critical gap?
Thanks,
Reza
On Thu, Oct 24, 2024, 9:38 AM Reza Rahman via jakarta.ee-community <jakarta.ee-community@xxxxxxxxxxx> wrote:
BTW I want to see how far I can push this forward by October 31, roughly when the Steering Committee Program Plan needs to be finalized. If you can at least post something on those mailing lists by then, I believe it will make some difference.
Please also consider steps to bring more quality into our existing releases to help EE applications to get more out of their code base including making changes in their applications. Any thoughts on how we could figure out what that could look like?
_______________________________________________
From: Reza Rahman <reza_rahman@xxxxxxxx>
Sent: Tuesday, October 22, 2024 11:37 AM
To: Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Subject: Fwd: [jakarta.ee-spec] Defining Jakarta EE 12 Scope in Program PlanDear Jakarta EE community,
I am asking for your help with this. You should chime in to the mailing lists below. Better yet, if you can somehow help make some of the work happen, that is simply outstanding.
Thanks,
Reza
-------- Forwarded Message --------
Subject: [jakarta.ee-spec] Defining Jakarta EE 12 Scope in Program Plan Date: Tue, 22 Oct 2024 11:30:50 +0200 From: Reza Rahman via jakarta.ee-spec <jakarta.ee-spec@xxxxxxxxxxx> Reply-To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx> To: jakarta.ee-spec@xxxxxxxxxxx, jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> CC: Reza Rahman <reza_rahman@xxxxxxxx>, jakarta.ee-wg@xxxxxxxxxxx, JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Hi folks,
I would like to see if we can define clear, compelling, and specific
scope for Jakarta EE 12 as part of the Steering Committee Program Plan:
https://docs.google.com/presentation/d/1xUNDHMP_qTHH1wA3m0yCmWVf_sHp41Qd7Opq3FhgINs/edit?usp=sharing.
I believe this is of critical importance at this juncture. If I did not
think so, I would not bother trying. I have detailed all the rationale
here:
https://docs.google.com/document/d/1U2qEqF9K969t5b3YuX4cwex5LJPvF3bt1w27cdKNpDM/edit?usp=sharing.
For those that recall, something very similar was done for Jakarta EE
11, so this isn't exactly without precedent.
I would like to see if this can be done in the following couple of
weeks, when the Program Plan is due.
Thanks,
Reza
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
Reza Rahman
Principal Program Manager
Java on Azure at Microsoft
+1 717 329 8149
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community