Back with a fresh blog on Maven – no saga, just a simple update on an old project of mine. It’s like catching up with an old buddy and sharing what’s new. In this blog, we’ll dive into the world of Maven, exploring the tweaks and improvements I’ve made to an old favorite. Whether you’re a Maven pro or just getting started, let’s take a stroll through My Maven adventure together!
TL;DR
- The Challenge: Figuring out how to upgrade an application server in a project with lots of parts using Ant.
- The Solution: Use Maven’s Multi-Module plan and a Bill Of Materials (BOM) to control versions in one place, making upgrades and managing parts easier.
- The Journey: Facing issues like circular dependencies and copying projects, Maven’s tools, and multi-module system helped a lot.
- Key Takeaways: Sharing practical lessons learned during the move, showing how Maven made the project better and ready for more improvements.
Once Upon a Time in Engineering
In a tech adventure, I have been tasked to upgrade the Application Server for a product used on servers like Glassfish or WebLogic. The goal? Boost security and prepare for future JDK upgrades. The product included 20+ EJB projects and 20+ war projects packed into an EAR.
This article has been indexed from DZone Security Zone