# Jakarta EE Published articles for Jakarta EE. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Java Weekly, Issue 668 DevFeed: [Java Weekly, Issue 668]() Original publisher: [Read original article]() Author: baeldung Published: 2026-10-18T07:13:23Z Content type: article Language: en Sources: [Baeldung]() Topics: [openjdk](), [Agent Harness](), [Quarkus](), [CI/CD]() Tags: [agents](), [ai-agents](), [coding-agents](), [jakarta-ee](), [java](), [jdk](), [jdk-28](), [kotlinconf](), [micronaut](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 668 is a roundup of Java and software development links. It highlights JDK 28, Java runtimes and coding-agent harness experiments, alongside articles, talks, and releases covering Java frameworks, testing, concurrency, GPU computing, and software design. ### Source excerpt JDK 28 is shaping up nicely. And an interesting harness experiment. The post Java Weekly, Issue 668 first appeared on Baeldung. ## Java News Roundup: JobRunr 9, OpenXava 8, Quarkus, LangChain4j, JNoSQL, Introducing Lathe DevFeed: [Java News Roundup: JobRunr 9, OpenXava 8, Quarkus, LangChain4j, JNoSQL, Introducing Lathe]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-10-05T17:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [releases](), [IntelliJ IDEA](), [google-adk](), [langchain4j](), [Micronaut](), [Quarkus]() Tags: [adk](), [architecture-design](), [development](), [eclipse-jnosql](), [google-adk-for-java](), [google-adk-for-kotlin](), [jakarta-ee](), [java](), [java-language](), [java-news-roundup-sep28-2026](), [jdk-28](), [jobrunr](), [kotlin](), [langchain4j](), [lathe](), [micronaut](), [news](), [openxava](), [point-releases](), [quarkus](), [releases]() ### AI overview This Java news roundup covers releases and updates across Java libraries, frameworks, and developer tools, including JobRunr, OpenXava, Quarkus, Micronaut, LangChain4j, Eclipse JNoSQL, and Google's Agent Development Kit. It also reports on OpenJDK's JEP 544 targeting JDK 28 and introduces Lathe, a Java language server that uses a Maven build model and supports LSP-compatible editors. ### Source excerpt This week's Java roundup for September 28th, 2026, features news highlighting: the GA releases of JobRunr 9.0 and OpenXava 8.0; point releases for Quarkus, Micronaut, LangChain4j, Eclipse JNoSQL; ADK for Java and ADK for Kotlin; and introducing Lathe, a new Java language server. By Michael Redlich ## Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts DevFeed: [Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts]() Original publisher: [Read original article]() Author: Jeff Beck Published: 2026-09-28T13:01:50Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [rhel](), [Spring Framework](), [WebSocket]() Tags: [application-modernization](), [deprecated](), [jakarta-ee](), [java](), [release](), [runtimes](), [web-server]() ### AI overview Red Hat JBoss Web Server 7 upgrades to Apache Tomcat 11.0.21, Jakarta EE 11, and Java 17. The article explains application and deployment changes, including updates to expression-language record handling, Servlet response APIs, and parameter parsing behavior that may require code changes before deployment. ### Source excerpt Upgrading your web server layer can mean an afternoon of dependency updates or 3 months of effort troubleshooting breaking changes. With Red Hat JBoss Web Server (JWS) 7 now generally available--bringing Apache Tomcat 11.0.21, Jakarta EE 11, and Java 17--here is what actually impacts your builds and deployments. The post Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts appeared first on Red Hat Developer. ## Java News Roundup: TornadoVM 7.0, Groovy 6.0, GraalVM, Hibernate, Quarkus, Gradle, Maven DevFeed: [Java News Roundup: TornadoVM 7.0, Groovy 6.0, GraalVM, Hibernate, Quarkus, Gradle, Maven]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-28T02:30:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [TornadoVM](), [Java](), [Groovy](), [openjdk](), [Gradle](), [Maven](), [Micronaut](), [Quarkus](), [Spring Framework](), [Jakarta EE](), [jooq](), [JDK Flight Recorder]() Tags: [2026](), [architecture-design](), [beta](), [candidate](), [development](), [graalvm](), [gradle](), [groovy](), [hibernate](), [hibernate-orm](), [jakarta-ee](), [java](), [java-news-roundup-sep21-2026](), [jdk-28](), [jvm](), [maven](), [micrometer](), [micronaut](), [news](), [open-jdk](), [open-liberty](), [point-releases](), [quarkus](), [quarkus-test](), [release](), [tornadovm](), [tracing]() ### AI overview This Java news roundup covers releases and development updates across the Java ecosystem, including TornadoVM 7.0 and Groovy 6.0, along with updates to GraalVM, Gradle, Quarkus, Micronaut, Maven, Micrometer, Open Liberty and Hibernate ORM. It also reports on JDK Enhancement Proposals for ahead-of-time compilation and adaptive heap sizing for ZGC. ### Source excerpt This week's Java roundup for September 21st, 2026, features news highlighting: GA releases of TornadoVM 7.0 and Groovy 6.0; point releases of GraalVM and Gradle; maintenance releases of Quarkus and GDK for Micronaut; the seventh release candidate of Maven 4.0; milestone releases of Micrometer Metrics and Tracing; and beta releases of Open Liberty and Hibernate ORM. By Michael Redlich ## Java News Roundup: JDK 27, Open J Proxy, A2A Jakarta, Azul Payara, BoxLang, Netflix ja DevFeed: [Java News Roundup: JDK 27, Open J Proxy, A2A Jakarta, Azul Payara, BoxLang, Netflix ja]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-21T17:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [releases](), [Jakarta EE](), [database-scalability](), [Command-line interface](), [connection pool](), [JavaFX](), [Cache]() Tags: [agent2agent](), [architecture-design](), [azul-payara](), [boxlang](), [cache](), [command-line](), [connection-pool](), [database-scalability](), [developer](), [development](), [jakarta-ee](), [java](), [java-news-roundup-sep14-2026](), [javafx](), [jdk](), [jdk-27](), [jdk-28](), [jetbrains](), [jhipster](), [ktor](), [libericajdk](), [netflix](), [news](), [open-j-proxy](), [proxy](), [release](), [releases]() ### AI overview A weekly roundup of Java ecosystem news covering the general availability of JDK 27, early-access JDK 28 builds, Liberica JDK 27, Jakarta EE 12 planning, Open J Proxy 1.0, and releases from several Java-related projects. It also introduces Netflix ja, a JMS command-line development experience for Java developers. ### Source excerpt This week's Java roundup for September 14th, 2026, features news highlighting: the GA release of JDK 27, LibericaJDK 27, Open J Proxy 1.0 and A2A Jakarta 1.0; point releases of Azul Payara, JHipster, JetBrains Ktor and BoxLang; and introducing Netflix ja, a modern JMS command line development experience for Java developers. By Michael Redlich ## Java News Roundup: New OpenJDK JEPs, CDI 5.0, Spring, Open Liberty, RefactorFirst, ADK for Kotlin DevFeed: [Java News Roundup: New OpenJDK JEPs, CDI 5.0, Spring, Open Liberty, RefactorFirst, ADK for Kotlin]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-14T20:15:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [Concurrency](), [releases](), [Jakarta EE](), [Gradle](), [Groovy]() Tags: [2026](), [architecture-design](), [concurrency](), [development](), [gradle](), [groovy](), [jakarta-ee](), [java](), [java-news-roundup-sep07-2026](), [jdk-27](), [jdk-28](), [kotlin](), [micronaut](), [news](), [open-jdk](), [open-liberty](), [refactorfirst](), [releases](), [spring-framework](), [tornadovm]() ### AI overview A Java news roundup for September 7, 2026, covers new OpenJDK proposals for ahead-of-time compilation and structured concurrency, Jakarta CDI 5.0 and ADK for Kotlin 1.0, Open Liberty, TornadoVM, RefactorFirst, Micronaut, Groovy 6.0, and Gradle 9.8. It also reports current JDK 27 and JDK 28 early-access builds and describes improvements in TornadoVM 6.1.0. ### Source excerpt This week's Java roundup for September 7th, 2026, features news highlighting: new JEPs for ahead-of-time compilation and structured concurrency; GA releases of Jakarta CDI 5.0 and ADK for Kotlin 1.0; the September 2026 edition of Open Liberty; point releases of TornadoVM and RefactorFirst; a maintenance release of Micronaut; and first releases candidates of Groovy 6.0 and Gradle 9.8. By Michael Redlich ## Meet Jos Roseboom DevFeed: [Meet Jos Roseboom]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2026-09-11T04:23:25Z Content type: article Language: en Sources: [Vlad Mihalcea]() Topics: [performance-engineering](), [coding-community](), [Tool](), [SINGAJUG](), [AI Chat](), [software-development]() Tags: [2026](), [ai](), [ai-agents](), [boot](), [community](), [conference](), [developers](), [ee](), [framework](), [hibernate](), [interview](), [jakarta-ee](), [java](), [jpa](), [micronaut](), [performance](), [performance-tuning](), [play](), [quarkus](), [spring]() ### AI overview Jos Roseboom describes two recurring production problems he encountered: requests exhausted all database connections while waiting on a failing external system, leaving the application unresponsive; and an application became very slow because it fetched entities and traversed associations, issuing far too many queries. He traces the latter to assuming Hibernate removes the need to understand SQL. The excerpt frames these as lessons from repeated incidents across companies, but does not include his full interview or the tuning remedies. ### Source excerpt JavaZone 2026 At the beginning of September, I participated in JavaZone for the third time and had the privilege of meeting a lot of passionate software developers willing to share their knowledge with the community. In the first conference day, I attended a very good talk about JPA performance tuning that was delivered by Jos Roseboom and since I enjoyed his talk, I proposed him to gave an interview for this blog. Therefore, in this article we have the pleasure of getting to know Jos and take opportunity of learning about Spring... Read More The post Meet Jos Roseboom appeared first on Vlad Mihalcea. ## GitHub Copilot SDK for Java: Annotations, Virtual Threads, and BYOK for Enterprise Agent Harnesses DevFeed: [GitHub Copilot SDK for Java: Annotations, Virtual Threads, and BYOK for Enterprise Agent Harnesses]() Original publisher: [Read original article]() Author: Developers Digest Published: 2026-08-11T00:00:00Z Content type: release Language: en Sources: [Developers Digest]() Topics: [GitHub Copilot SDK](), [SDK](), [GitHub](), [Java](), [Concurrency](), [Jakarta EE](), [Spring Boot]() Tags: [ai-agents](), [enterprise](), [github](), [github-copilot](), [github-copilot-sdk](), [jakarta-ee](), [java](), [news](), [openai](), [preview](), [sdk](), [spring](), [threads]() ### AI overview GitHub shipped a preview Java-native Copilot SDK with @CopilotTool annotations, virtual-thread support, Jakarta EE and Spring composition, and BYOK mode for OpenAI-compatible endpoints without requiring a Copilot subscription. ### Source excerpt GitHub shipped a Java-native Copilot SDK (1.0.7-preview.1) with @CopilotTool annotations, virtual-thread support, Jakarta EE and Spring composition, and BYOK mode that works against any OpenAI-compatible endpoint with no Copilot subscription. Here is what changed and what it unlocks. ## Using the GitHub Copilot SDK for Java DevFeed: [Using the GitHub Copilot SDK for Java]() Original publisher: [Read original article]() Author: Edward Burns Published: 2026-08-10T19:30:00Z Content type: tutorial Language: en Sources: [GitHub Blog](), [GitHub Engineering]() Topics: [GitHub Copilot SDK](), [SDK](), [Jakarta EE](), [Spring Framework](), [langchain4j](), [GitHub Copilot CLI]() Tags: [agent-harness](), [ai](), [ai-ml](), [application](), [copilot](), [engineering](), [github](), [github-copilot](), [github-copilot-sdk](), [house](), [jakarta-ee](), [java](), [lead-management](), [london](), [sdk](), [threads](), [virtual](), [virtual-threads]() ### AI overview The GitHub Copilot SDK for Java lets server-side Java code create Copilot agent sessions, register tools, send prompts, and receive structured responses programmatically. The post presents it as framework agnostic, usable with Jakarta EE or Spring, and AI vendor neutral through BYOK; it contrasts this with dependencies on Langchain4j or Spring AI. The SDK uses familiar Java features including annotations, lambdas, and virtual threads. The sample is a Jakarta EE 11 real-estate lead-management pipeline that starts an isolated Copilot agent on a virtual thread to process customer enquiries. Requirements listed are JDK 17 or 25 (25 recommended), Maven 3.9+, an active Copilot subscription, and Copilot CLI 1.0.71 or later. ### Source excerpt Enterprise Java developers have a new superpower--drive GitHub Copilot from idiomatic Java code with annotations, virtual threads, and more. The post Using the GitHub Copilot SDK for Java appeared first on The GitHub Blog. ## The best way to replace the deprecated GenericGenerator DevFeed: [The best way to replace the deprecated GenericGenerator]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-12-02T08:23:12Z Content type: tutorial Language: en Sources: [Vlad Mihalcea]() Topics: [GenericGenerator](), [software-development](), [Legacy Modernization]() Tags: [ai](), [annotation](), [boot](), [custom](), [database-identifier](), [deprecated](), [genericgenerator](), [hbm](), [hibernate](), [how-to](), [identifier](), [jakarta-ee](), [java](), [jpa](), [micronaut](), [performance](), [play](), [tsid](), [xml]() ### AI overview Hibernate's `@GenericGenerator`, deprecated in favor of `@IdGeneratorType`, served two main purposes: defining a custom identifier generator and supplying a sequence optimizer. The excerpt focuses on replacing custom identifier generation: it uses a time-sorted ID (TSID) generator and explains that `@IdGeneratorType` enables a custom annotation on an entity attribute so Hibernate can generate IDs during persistence. The article says Hypersistence Utils already provides the needed classes, while introducing the meta-annotation mechanism. The supplied excerpt cuts off before the example is complete, so it does not establish the full mapping or the sequence-optimizer replacement. ### Source excerpt Introduction In this article, I'm going to show you the best way to replace the deprecated @GenericGenerator when upgrading your application to Hibernate 7. Hibernate @GenericGenerator annotation The @GenericGenerator annotation has been available since Hibernate 3.5, as an alternative to the XML element from HBM mappings. As illustrated by the Hibernate 6.5 @GenericGenerator Javadoc, this annotation was deprecated in favor of the @IdGeneratorType meta-annotation, which we've been using before for the TSID identifier. Traditionally, there were two main use cases where you'd use the @GenericGenerator annotation: to provide a custom identifier... Read More The post The best way to replace the deprecated GenericGenerator appeared first on Vlad Mihalcea. ## Foundations of AI and Machine Learning for Java Developers Course Review DevFeed: [Foundations of AI and Machine Learning for Java Developers Course Review]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-04-11T08:26:55Z Content type: article Language: en Sources: [Vlad Mihalcea]() Topics: [Artificial Intelligence](), [Machine learning](), [Learning](), [Large Language Model](), [AI Development]() Tags: [ai](), [ai-and-machine-learning](), [article](), [artificial-intelligence](), [course](), [design-patterns](), [developers](), [foundations](), [genai](), [generative-ai](), [hibernate](), [jakarta-ee](), [java](), [jpa](), [language-models](), [large-language-models](), [learning](), [llm](), [machine-learning](), [ml](), [review]() ### AI overview Frank Greco's Foundations of AI and Machine Learning for Java Developers is a 1-hour-35-minute video course for learners new to AI and ML. Its agenda moves from machine-learning foundations and AI taxonomy to predictive AI with JSR #381 Visual Recognition, including code to train and use a model. It then covers generative AI, large language models, prompts and context, retrieval-augmented generation, and ways to access LLM services through stateless REST APIs, with Java and LC4J examples and a demo. The excerpt also lists software development patterns and determinism versus...; the agenda is cut off there, so later material cannot be summarized. The article says LinkedIn Learning offered the course free until June 20, without specifying a year. ### Source excerpt Introduction In this article, I'm going to review the Foundations of AI and Machine Learning for Java Developers video course from my fellow Java Champion, Frank Greco. If you are new to AI and ML and want to get a great introduction to these topics, then you should definitely join watch the video lessons created by Frank Greco. And, thanks to LinkedIn Learning's generosity, until June 20, you can enroll in this video course for free. Video Course Agenda The course provides one hour and thirty-five minutes of video lessons that are... Read More The post Foundations of AI and Machine Learning for Java Developers Course Review appeared first on Vlad Mihalcea. ## Java 17 will be the minimum version for Quarkus 3.7 DevFeed: [Java 17 will be the minimum version for Quarkus 3.7]() Original publisher: [Read original article]() Author: Max Rydahl Andersen (https://twitter.com/maxandersen) Published: 2023-11-30T00:00:00Z Content type: release Language: en Sources: [Quarkus - Supersonic Subatomic Java]() Topics: [Java](), [Quarkus](), [version](), [deprecated](), [migration]() Tags: [deprecated](), [jakarta-ee](), [java](), [java-17](), [making](), [migration](), [quarkus](), [release](), [version]() ### AI overview Quarkus announces that Quarkus 3.7 will require Java 17 as the minimum JDK for building and running Quarkus applications. Users who cannot migrate immediately can continue with Quarkus 3.6 or use the Quarkus 3.2 LTS stream, while Java 17 users are unaffected. ### Source excerpt Today we are anouncing that Quarkus 3.7 will move Quarkus to use Java 17 as the minimum JDK. When we started Quarkus 3.0, we stayed on Java 11. The feedback we got was that moving to Jakarta EE 10 was for many easier than to also move the underlying JDK. We wanted to give the ecosystem time to catch up and make sure we had a good story for users that needed to stay on Java 11. In 3.0 release, we supported Java 11 for Quarkus core, and we marked Java 11 as deprecated. It should be noted that parts of the platform, especially the Camel Extensions for Quarkus, already require Java 17. Today we are taking the step to move Quarkus core to Java 17 as the minimum JDK for Quarkus 3.7 and onwards. This means that Quarkus 3.7 will require Java 17 to build and run all Quarkus applications. Below are some of the reasons for this decision and what it means for you as a Quarkus user. Everyone is using Java 11 - you cannot do this! We know that many users are still using Java 11 and we are not forcing you to move to Java 17. We are just making it the minimum version for Quarkus 3.7 and onwards. That said - the usage data development builds in the last 30 days shows less than 8% using Java 11 for Quarkus Development. We expect the Java 11 number to be higher in production but the trend is clear - Java 11 usage is low and declining. If you like to help us get more accurate data for future, then please consider contributring anonymous build time data - see quarkus.io/usage for details. I cannot move to Java 17 yet, what should I do? If you cannot move to Java 17 yet, then you can continue to use Quarkus 3.6, but we recommend you consider to use the Quarkus 3.2 LTS stream as that is the version that will get updates and fixes for the longest. Be mindful though that Java 11 itself is rapidly heading towards going out of full support. Example Red Hat's full Java 11 support ends in October 2024 and Oracle ended Premier support in September 2023. Thus we highly recommend you start plannin ## Keycloak 22.0.0 released DevFeed: [Keycloak 22.0.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2023-07-11T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [releases](), [Release notes](), [Quarkus](), [Jakarta EE](), [Hibernate](), [Java](), [upgrade](), [deprecated]() Tags: [deprecated](), [hibernate](), [idm](), [jakarta-ee](), [java](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [openid-connect](), [quarkus](), [release](), [release-notes](), [saml](), [sso](), [upgrade]() ### AI overview Keycloak 22.0.0 removes Java 11 support, upgrades to Quarkus 3.x and Hibernate ORM 6.2, migrates from Java EE to Jakarta EE 10, and adds a KeyStore Vault implementation and KeyStore Config Source. ### Source excerpt To download the release go to Keycloak downloads. Release notes Server Distribution Java 11 support removed Running the Keycloak server with Java 11 is no longer supported. Java 11 was deprecated in Keycloak 21 with the announced plan to be removed in Keycloak 22. Upgrade to Quarkus 3.x Keycloak upgraded to version 3.2.0.Final of the Quarkus Java framework. Quarkus 3.x continues the tradition of propelling Java development by moving fast and providing a cutting-edge user experience with the latest technologies. Transition from Java EE to Jakarta EE As part of upgrading to Quarkus 3.x Keycloak migrated its codebase from Java EE (Enterprise Edition) to its successor Jakarta EE, which brings various changes into Keycloak. We have upgraded all Jakarta EE specifications in order to support Jakarta EE 10. Context and dependency injection no longer enabled to JAX-RS Resources In order to provide a better runtime and leverage as much as possible the underlying stack, all injection points for contextual data using the javax.ws.rs.core.Context annotation were removed. The expected improvement in performance involves no longer creating proxies instances multiple times during the request lifecycle, and drastically reducing the amount of reflection code at runtime. Upgrade to Hibernate ORM 6 Keycloak now benefits from the upgrade to Hibernate ORM 6.2, which includes improved performance, better SQL, modern JDK support, and support for modern RDBMS features. Elytron credential store replacement The previous and now removed WildFly distribution provided a built-in vault provider that reads secrets from a keystore-backed Elytron credential store. As this is no longer available, we have added a new implementation of the Keycloak Vault SPI called Keycloak KeyStore Vault. As the name suggests, this implementation reads secrets from a Java keystore file. Such secrets can be then used within multiple places of the Administration Console. For further details, see our guide and the latest ## How to migrate applications to Quarkus 3 with the Quarkus Update Tool DevFeed: [How to migrate applications to Quarkus 3 with the Quarkus Update Tool]() Original publisher: [Read original article]() Author: Martin Kouba (https://twitter.com/martunek) Published: 2023-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Quarkus - Supersonic Subatomic Java]() Topics: [Quarkus](), [migration](), [Jakarta EE](), [Java](), [Command-line interface](), [make](), [Maven]() Tags: [cli](), [code](), [gradle](), [guide](), [jakarta-ee](), [java](), [maven](), [migration](), [quarkus](), [upgrade]() ### AI overview This tutorial explains how to migrate applications to Quarkus 3, including the transition from javax.* to jakarta.* packages and updates to related dependencies and extensions. It describes using the Quarkus Update Tool through the Quarkus CLI, Maven, or Gradle, and notes that the tool writes changes directly to the file system. ### Source excerpt Quarkus 3 is out and we encourage our users to upgrade their applications to experience the best Quarkus ever! The team worked hard to deliver a lot of new features and performance improvements. But of course, there are also some breaking changes. The migration guide describes all the important changes in the core extensions. Nevertheless, there is also some tedious work that needs to be done. Quarkus 3 has updated to the latest Jakarta EE 10 APIs, which include the infamous change of the javax.* to the jakarta.* packages. If your application makes use of any Jakarta API, and there's a good chance it does (think about JAX-RS, CDI, JPA, etc.), you'll need to modify your code. Furthermore, if there's an explicit Jakarta API dependency in the project, you'll need to update this dependency as well. Of course, you can migrate the application manually. But since Quarkus embraces the developer joy there is the Quarkus Update Tool to the rescue! This blog post was written just after the Quarkus 3.0 release. Things have evolved a bit since then. For more information about how to update to the latest Quarkus, have a look at the dedicated guide. You can also find all the migration guides in our wiki. Quarkus Update Tool - TL;DR Install the Quarkus CLI or make sure the latest version is installed Run quarkus update Check the changes made by the tool Profit! Quarkus Update Tool - The Full Story The goal of the update tool is to help developers to migrate an application to Quarkus 3 smoothly. The update process can be triggered from the Quarkus CLI, and directly via Maven or Gradle commands. The tool itself is basically a set of OpenRewrite transformation rules. Most of the rules are defined in the Quarkus Update Recipes project. What exacty does the update tool do? Updates the Quarkus version Transforms the source code to use the jakarta.* packages Upgrades the Quarkiverse extensions to the versions compatible with Quarkus 3.0 Updates the Java EE API dependencies to the Jakarta ## Quarkus 3.0, our new major release, is here! DevFeed: [Quarkus 3.0, our new major release, is here!]() Original publisher: [Read original article]() Author: Guillaume Smet (https://twitter.com/gsmet\_) Published: 2023-04-26T00:00:00Z Content type: release Language: en Sources: [Quarkus - Supersonic Subatomic Java]() Topics: [Quarkus](), [Jakarta EE](), [Java](), [software-development](), [upgrade](), [User Interfaces](), [Open Source]() Tags: [developer-experience](), [extensions](), [jakarta-ee](), [java](), [major](), [new-features](), [open-source](), [quarkus](), [release](), [upgrade](), [version]() ### AI overview Quarkus 3.0 is a major release based on Jakarta EE 10, with a redesigned and more extensible Dev UI, migration from javax.* to jakarta.* packages, MicroProfile 6 alignment, and an upgrade to Hibernate ORM 6.2. ### Source excerpt Quarkus 3.0 is the result of a lot of work and dedication from the community. Quarkus continues to be an Open Source stack to write Java applications offering unparalleled startup time, memory footprint, and developer experience. The development of Quarkus 3 started last year on March 18, 2022, with the crazy idea that we could rewrite the whole tree to migrate to the new jakarta.* packages while continuing the development of Quarkus 2. Quarkus 3.0 is based on Jakarta EE 10 and, as you can expect, it is not the only change. This version comes packed with new features and enhancements that we implemented during this period. This announcement contains a lot of information about the new features and how to upgrade so we recommend reading it thoroughly before upgrading to Quarkus 3. What's new? New Dev UI Quarkus 2 introduced the Dev UI, which provides a web UI to use during development. Extensions could provide their own Dev UI pages to provide additional functionality. Quarkus 3.0 now has a new Dev UI that is more extensible and easier to use. It also has a new and much-improved look and feel. The new Dev UI is available by default. However, because not all the extensions have migrated to the new Dev UI, you can still access the old one at /q/dev-v1. The old Dev UI is planned for removal in a future version. We have a playlist on Quarkus YouTube channel that shows off the new Dev UI, explains the new features and how to use and extend it. Jakarta EE 10 Quarkus 2 was based on Jakarta EE 8. Quarkus 3 is based on Jakarta EE 10. The most visible change is that the javax.* packages from Jakarta EE have been moved to jakarta.*. This change requires changing any source code and dependency and its transitive dependencies that rely on the javax.* packages. See the Updating to Quarkus 3.0 section for more information on how quarkus update helps you migrate. The change to target Jakarta EE 10 brings two major improvements: The broader Java ecosystem is moving to Jakarta dependen