110 Java Maven Best Practices

This one walks through your Maven POMs and flags the usual suspects: hardcoded versions that should live in dependencyManagement, plugin config that belongs in pluginManagement, and properties scattered across child modules instead of centralized in the parent. It's smart about multi-module projects and actually reads every child POM before making recommendations, which matters when you're hunting version drift across siblings. The workflow is cautious: it runs mvn validate first and won't touch anything if your build is already broken. Written by Juan Antonio Breña Moral as part of the cursor-rules-java project. Solid if you inherit a messy Maven setup or want to clean up before it gets worse.