Re: [jakartaee-platform-dev] Defining Jakarta EE 12 Scope in Program Pla

[Ryan Cuprak <rcuprak@xxxxxxx>]

I like the document.

I agree on the deprecation and removal of old technologies. However, EE is know for stability and we don’t want too aggressive.

I propose a tool that will scan an EE application and will give a health report. If people share these health reports, we can get a sense of the impact of a deprecation and removal. 

There has to be an incentive for removal as we don’t want to increase Jakarta EE developmental costs unnecessarily. Java EE / Jakarta EE got a black eye for the namespace migration. For large organizations it was undoubtedly expensive. 

 What does removing EJB get us? CDI doesn’t fully replace it yet. 

-Ryan

> On Oct 22, 2024, at 5:30 AM, Reza Rahman via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
> 
> 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
> 
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev