Staying Current A Journey in Software Maintenance
summary
Describes a concrete maintenance pipeline that centralizes common libs and replaces a parent POM with an automated toolchain: a homegrown fly CLI that scaffolds POMs, Dockerfiles and GitHub workflows, Spring Application Advisor + OpenRewrite recipes that produce upgrade plans and open PRs, and scheduled CI that runs 15–60 minutes per upgrade. It reports faster onboarding, automation of code fixes (some tests fail and require review), and current rollout across about 5–10 repositories.
AI-written summary · about
chapters (12)
- 0:00Introduction to maintenance
- 1:11Why staying current is harder
- 2:37First approach standardization
- 5:26Limitations of parent POM
- 5:49Tools for automation
- 7:12Developer maintenance struggles
- 7:53CLI tool overview
- 12:07CLI tool demonstration
- 21:21Spring Boot upgrades
- 22:03Spring Application Advisor demo
- 30:56Future improvements
- 32:01Q&A session
related talks
57mSurvival guide to continuously align and upgrade your Spring dependencies
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
47mProject Talk: Maintenance Update
01h 17mRefactoring the ROI of Software
57mRefactoring to Modernize Java Applications
33mKeep your dependencies in check
24mRichard Gross Head of Software Archeology, MaibornWolff
59mModernize Software and Tackle Tech Debt at Big Bank Scale