[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-spec] [jakarta.ee-wg] [External] : Defining Jakarta EE 12 Scope in Program Plan
|
OK. So, it sounds like Will is absolutely right in re-surfacing
this conversation for EE 12.
On 1/14/2025 9:15 AM, Arjan Tijms
wrote:
Hi,
It was platform wide, but not done comprehensively. Some
teams forgot about it, and then refused to do it for Jakarta
EE 11 still (using a service release). The reason for refusal
was almost always that they didn't see value in removing the
security manager for Jakarta EE 11.
Kind regards,
Arjan Tijms
Ed,
Do you know to what extent the Security Manager
dependency removal work was done in EE 11? I know at least
some work was done, but was it really platform wide,
comprehensive, and consistent across specifications?
Thanks,
Reza
On 1/13/2025 4:50 PM, Will Lyons wrote:
All –
I
don’t know if this topic has been covered so
capturing it here.
If
Jakarta EE 12 will be supported on Java 21 and Java
25, we will need to review the implications of
features that are likely to be removed, including
the following:
JEP 486: Permanently Disable
the Security Manager
https://openjdk.org/jeps/486
https://inside.java/2024/12/11/quality-heads-up/
My
understanding is that some Jakarta EE specifications
have a dependency on Java Security Manager,
especially Connector. The implications of this
removal, and the alternative actions in response,
should be identified.
Thanks
Will
_______________________________________________
jakarta.ee-wg mailing list
jakarta.ee-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-wg