pom-ordering

Maven pom.xml files should organize dependencies by scope (compile, runtime, test) and then by groupId using region comments. This Skill enforces that structure automatically, grouping first-party dependencies, then third-party libraries like Liftwizard and Dropwizard, creating a consistent, readable hierarchy that reduces merge conflicts.

Region comments mark logical dependency groups in pom.xml, making files easier to navigate and maintain. They separate concerns—compile dependencies from test dependencies, first-party from third-party—so developers quickly find what they need without scanning the entire dependency list.

Yes. This Skill automatically reorders and structures pom.xml dependencies according to standard grouping rules: by scope first, then by groupId, with region comments marking each section. It applies these rules consistently across your Maven projects without manual intervention.

Nested regions support granular organization within dependency groups—for example, separating Liftwizard runtime dependencies from Liftwizard config dependencies. This Skill applies nested region blocks to keep related libraries grouped while maintaining the larger scope and groupId hierarchy.

Inconsistent ordering causes developers to add dependencies in different positions, creating merge conflicts. Enforcing strict ordering—by scope, then groupId, with region comments—ensures all contributors place dependencies in the same location, eliminating conflicts and keeping pom.xml stable.

Yes. The Skill recognizes first-party dependencies using ${project.groupId} and project modules, placing them first in the dependency order. This ensures module interdependencies are clearly separated from third-party libraries in multi-module builds.