build: order pom.xml properties per TFMC conventions - #25
Conversation
Put maven.compiler.release and project.build.sourceEncoding first, then maven.compiler.proc, then the remaining properties alphabetically. The effective POM is unchanged apart from property order. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Limit details: You’ve used all 10 included reviews currently available. 📝 SummarySummary by CodeRabbit
WalkthroughThe ChangesMaven properties
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to No build behavior change is identified in the property reorder, so no merge-blocking issue remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
Usage-based review receipt
Note This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews. Comment |
Summary
Part of a cross-repository audit against the TF-Minecraft repository norms (README layout per Docs MAINTAINING.md and the other plugin READMEs, POM layout per Docs POM-CONVENTIONS.md).
pom.xml: order properties per Docs POM-CONVENTIONS.md:maven.compiler.release,project.build.sourceEncoding,maven.compiler.proc, then the rest alphabetically (see docs: place maven.compiler.proc after the encoding property Docs#87).Checks
maven-help-plugin:3.5.2:effective-pom, offline) compared before and after: identical apart from property order.🤖 Generated with Claude Code