# Java 17 Published articles for Java 17. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Trino's Upgrade to Java 24 DevFeed: [Trino's Upgrade to Java 24]() Original publisher: [Read original article]() Author: Manfred Moser, Mateusz Gajewski Published: 2025-03-03T00:00:00Z Content type: opinion Language: en Sources: [Trino Blog]() Topics: [Java](), [upgrade](), [Security](), [Kafka](), [phoenix]() Tags: [java](), [java-17](), [kafka](), [phoenix](), [release-notes](), [security](), [upgrade]() ### AI overview The article discusses Trino's upgrade from Java 23 to Java 24, highlighting selected Java 24 features and the expected impact of permanently disabling the Security Manager on Trino connectors and dependencies. ### Source excerpt Six month ago we adopted Java 23 as requirement, following our standard procedure to upgrade with each Java version as soon as it becomes available. This allows us to take advantage of all the great improvement each release brings. The upgrade to 23 was pretty easy since the changes from 22 to 23 were not that big. The story turns out to be a bit different now with our upgrade to Java 24. ## Keycloak 21.1.0 released DevFeed: [Keycloak 21.1.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2023-04-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [releases](), [Release notes](), [monorepo](), [Authorization](), [Java]() Tags: [copy](), [deprecated](), [idm](), [java-17](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [monorepo](), [openid-connect](), [release](), [release-notes](), [saml](), [sso](), [ui]() ### AI overview Keycloak 21.1.0 is a software release that migrates the project into a main GitHub repository, promotes FIPS 140-2 support to officially supported status, and introduces Account Console version 3 as an experimental feature. It also extracts the Policy Enforcer into a separate Java dependency and includes the Nashorn JavaScript engine by default. ### Source excerpt To download the release go to Keycloak downloads. Release notes Monorepo In the past Keycloak was maintained across multiple GitHub repositories: Documentation repository UI repository Node.js admin client repository Having multiple repositories introduced a lot of complexity and toil. For example frequently multiple pull requests had to be sent to different repositories for a single change. To simplify things we have now migrated everything into the main repository. FIPS 140-2 support FIPS 140-2 support in Keycloak, which was preview in the previous release, is now promoted to be officially supported. Experimental Account Console version 3 The Account Console version 3 is now available as an experimental feature in Keycloak. This version supports custom fields created with the 'User Profile' feature. If you are looking to try it out and provide us with some early feedback you can enable it as follows: bin/kc.sh start-dev --features=account3 Changes to Keycloak Authorization Services support in Keycloak Java-based Adapters As part of the removal of the deprecated adapters, the Keycloak Policy Enforcer was extracted from the adapters code base into a separate dependency: org.keycloak keycloak-policy-enforcer 21.1.0 By providing this dependency, we expect making it possible to integrate the policy enforcer with the Java stack of your preference. It also provides built-in support for enabling the policy enforcer to Jakarta applications protected with Wildfly Elytron. For now, this dependency is not yet GA as we are still working on the quickstarts and documentation. This work should not impact existing applications using the deprecated adapters. Javascript engine available by default In the previous version, when Keycloak was used on Java 17 with Javascript providers it was needed to add the Nashorn javascript engine to the distribution. This is no longer needed as Nashorn javascr ## 3.17.0 Release with Computed Columns, Audit Columns, Pattern Matching, Reactive Transactions and Kotlin Coroutine Support DevFeed: [3.17.0 Release with Computed Columns, Audit Columns, Pattern Matching, Reactive Transactions and Kotlin Coroutine Support]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-06-22T15:15:05Z Content type: release Language: en Sources: [jOOQ]() Topics: [releases](), [SQL](), [Kotlin](), [reactive](), [Transactions]() Tags: [audit-columns](), [client-side-computed-columns](), [computed-columns](), [coroutine](), [coroutines](), [implicit-join](), [java-17](), [jooq](), [jooq-3-17](), [jooq-development](), [kotlin](), [kotlin-coroutines](), [pattern-matching](), [postgresql](), [r2dbc](), [reactive-programming](), [reactive-transactions](), [release](), [release-notes](), [sql](), [stored](), [stored-computed-column](), [udt](), [virtual](), [virtual-computed-column]() ### AI overview The jOOQ 3.17.0 release adds client-side computed columns for read and write operations, audit columns, pattern-matching SQL transformations, and more implicit JOIN capabilities. It also sets Java 17 as the baseline for the Open Source Edition while commercial distributions continue supporting Java 8 and 11. ### Source excerpt This release contiues the work from previous releases around more sophisticated SQL transformation capabilities, including: Client side computed columns for both read and write operations Audit columns Pattern matching SQL transformations More implicit JOIN capabilities Client side computed columns A ground breaking new core feature available in all commercial distributions isthe new client side computed ... Continue reading 3.17.0 Release with Computed Columns, Audit Columns, Pattern Matching, Reactive Transactions and Kotlin Coroutine Support ->