Welcome to issue number three hundred and twenty-one of Hashtag Jakarta EE!
As this post comes out, I have just arrived home from DeveloperWeek 2026 in San Jose, California. I will now spend a couple of days at home before going to Montreal for ConFoo 2026. I look forward to presenting at this conference for the fifth time.
When drifting just a little outside the sphere of Java-focused conference, it is very apparent that Java is perceived as being a legacy language. Most of these developers (or do they identify as vibe-prompters these days?) are not aware of the progress made by Java to make it the number one platform for AI workloads. The performance of the JVM alone should be convincing enough, but these days when quality is measured by quantity (in lines of code), it is easy to forget the fundamentals of software architecture.
Bruno Borges has put together a bunch of patterns that showcases how modern Java differs from the old style, including how Enterprise Java has evolved from the old J2EE to modern Jakarta EE.
In the minutes from last week’s Jakarta EE Platform call, the content for Jakarta EE 12 Milestone 3 is outlined. All specifications are expected to update their parent pom.xml to the newly released EE4J Parent 2.0.0 which contains the configuration needed to be able to stage artifacts before releasing to Maven Central the same way we used to be able to do with OSSRH (which was retired last year).
By the way. If you were ever in doubt, this blog is, and will always be, 100% written by me. There is no AI involved, which you probably can tell by the spelling errors and (mostly) readable language. No generated slop here, only potentially sloppy human mistakes.
