home.social

#jdk11 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jdk11, aggregated by home.social.

  1. Proposal: Support Wayland and add KEM APIs

    [..] only Wayland will be supported in RHEL 10 and
    subsequent releases.
    [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algorithms.

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11 #JDK17

  2. Proposal: Support Wayland and add KEM APIs

    [..] only Wayland will be supported in RHEL 10 and
    subsequent releases.
    [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algorithms.

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11 #JDK17

  3. Proposal: Support Wayland and add KEM APIs

    [..] only Wayland will be supported in RHEL 10 and
    subsequent releases.
    [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algorithms.

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11 #JDK17

  4. Proposal: Support Wayland and add KEM APIs

    [..] only Wayland will be supported in RHEL 10 and
    subsequent releases.
    [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algorithms.

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11 #JDK17

  5. Proposal: Support Wayland and add KEM APIs

    [..] only Wayland will be supported in RHEL 10 and
    subsequent releases.
    [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algorithms.

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11 #JDK17

  6. There has been some interesting discussion on 11 and servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.

  7. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  8. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  9. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  10. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  11. The China Electronics Standardization Institute has recently published the mandatory standard GB 18030-2022 which requires additional code points available in Unicode 11.

    Proposal: Extend Unicode support for GB 18030-2022

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11

  12. The China Electronics Standardization Institute has recently published the mandatory standard GB 18030-2022 which requires additional code points available in Unicode 11.

    Proposal: Extend Unicode support for GB 18030-2022

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11

  13. The China Electronics Standardization Institute has recently published the mandatory standard GB 18030-2022 which requires additional code points available in Unicode 11.

    Proposal: Extend Unicode support for GB 18030-2022

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11

  14. The China Electronics Standardization Institute has recently published the mandatory standard GB 18030-2022 which requires additional code points available in Unicode 11.

    Proposal: Extend Unicode support for GB 18030-2022

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11

  15. The China Electronics Standardization Institute has recently published the mandatory standard GB 18030-2022 which requires additional code points available in Unicode 11.

    Proposal: Extend Unicode support for GB 18030-2022

    more @ mail.openjdk.org/pipermail/jdk

    #OpenJDK #JDK8 #JDK11

  16. Many #Java #OAuth2/#OIDC libraries tend to implement every single aspect of the standard, becoming quite huge and bringing a respectable amount of transitive dependencies with them.

    Time for a tiny zero-dependency library targeting desktop clients that need to run the "Authorization Flow for Native Apps" (#RFC8252) with either external or embedded browsers.

    Requires #JDK11 and contains a module-info.java, of course.

    github.com/coffeelibs/tiny-oau

  17. Many #Java #OAuth2/#OIDC libraries tend to implement every single aspect of the standard, becoming quite huge and bringing a respectable amount of transitive dependencies with them.

    Time for a tiny zero-dependency library targeting desktop clients that need to run the "Authorization Flow for Native Apps" (#RFC8252) with either external or embedded browsers.

    Requires #JDK11 and contains a module-info.java, of course.

    github.com/coffeelibs/tiny-oau