Java workloads can be efficient and secure at the same time. BellSoft Hardened Images with Liberica JDK Lite and Alpaquita Linux cut RAM and disk use by 30% and keep CVEs close to zero:

Ever wondered what really happens inside a buildpack? At JRush Ep.6, @patbaumgartner (@42talents) digs into Paketo internals and adds a custom AOT cache to make Spring Boot builds fly. Live on Nov 18: https://t.co/BPdjT5oTzj

🚀 Build a Spring Boot + Vaadin UI in 15 minutes: pure #Java, no JS. @cat_edelveis covers auth, lazy-loaded Grid, filters & dialogs, Binder validation, and a custom theme. Watch: https://t.co/elPC0ONm7Z

#KubeCon starts. We’re at stand 1253, already deep in conversations about startup times, container security, and what makes #Java tick in production. If you’re around, stop by and say hi, and we’ve got a Steam Deck raffle running too!

We’re doing something special with JRush this time. It’s all about containers – building faster, safer images, and understanding what really happens inside that build image. If you’ve ever fought slow builds or endless CVE noise, this one’s for you: https://t.co/BPdjT5proR

Introducing BellSoft Hardened Images, a new way to handle container security. OS, runtime, and CVE management all covered by one team under a single SLA. Up to 95% fewer CVEs and 30% less resource use for #Java workloads: https://t.co/wXqVlJa9ve

Heading to #VoxxedDays Thessaloniki 2025? Join @cat_edelveis for “From Cold Starts to Escape Velocity”, a deep look at GraalVM Native Image, CRaC and Project Leyden for faster #Java startup. Insightful, grounded, and focused on what actually works: https://t.co/hONdSNRl0f

If you’re at DevCon Romania, don’t miss @asm0di0 on stage in a couple of hours! He’ll be talking about “Crafting the Ultimate Spring Image” and how to turn your fat JAR into a fast, layered Docker build. 🕓 16:00 local time

New #LibericaNIK CPU builds are out – 23.0.10 (JDK 17), 23.1.9 (JDK 21), and 25.0.1 (JDK 25). Security & stability updates across java. security, jaxp, core-libc, and javafx modules. Stay secure. Stay current. 🔗 More info: https://t.co/pkssxWaFMZ ⬇️ Download:

🎃 Gather around, kids… it’s Halloween night.

Flaky JavaFX tests? Random NPEs? 🤕 @cat_edelveis explains the 7 most common TestFX mistakes: threading, Spring Boot setup, CI config, and more. Watch and make your UI tests reliable again: https://t.co/BLTQRmpnWd

Still on Java 8 or 11? This one’s for you. At Devoxx Belgium, @asm0di0 and @jbaruch shared how to make legacy #Java feel modern again: cleaner code, faster startup, better security. No rewrite needed:

The demo apps used Java 21 + TestFX + JUnit5 + AssertJ + Monocle. Full write-up with configs and explanations here:

Mistake 7: mixing domain logic with UI in tests. Business logic should live in view models and be tested with plain JUnit. Keep UI tests for rendering and interaction.

Mistake 6: misconfigured headless CI. Simply adding Monocle isn’t enough. Run with --add-opens, disable parallel UI tests, install native libs, and don’t assert fullscreen in headless.

Mistake 5: pixel-perfect equality across platforms. HiDPI, AA, GPU vs Monocle in CI → colors shift. Add tolerance and never assume an exact RGB match across OS/CI.

Mistake 4: racing the FX event queue. Assertions run before layout or scene switches complete. ❌ immediate assert ✅ wait for queue drain

Mistake 3: triggering handlers directly instead of simulating input. button. fire() bypasses pointer/focus bugs that real users hit.

Mistake 2: bootstrapping with mismatched loaders in Spring + TestFX. TestFX owns the Stage, Spring owns the beans. If you let FXMLLoader use the wrong loader, you’ll get NPEs. 📷

Mistake 1: touching UI off the FX thread. JUnit runs on its own thread, but only the FX thread can mutate controls.