chore: remove mvn-env wrappers; document Maven wrapper only - #1590
Conversation
Delete repo-root mvn-env.sh / mvn-env.bat (and the SC-004 sentinel that guarded them). Agents and docs were routinely confused by the dual wrapper paths; builds should use the standard Maven wrapper with JDK 21. - Replace all markdown references with ./mvnw / mvnw.cmd - Point scripts/docker/skills callers at mvnw (Windows: mvnw.cmd) - Clarify JAVA_HOME must be JDK 21 (wrapper no longer rewrites JAVA_HOME) - Drop scripts/test_mvn_env_untouched.py; update CodeQL path filters > Co-Authored by Grok Build using grok-4.5 with agent Grok.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (9 files)
Previous Review Summaries (5 snapshots, latest commit 0be3bd0)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 0be3bd0)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (9 files)
Fix these issues in Kilo Cloud Previous review (commit 6a19674)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
WARNING
Files Reviewed (233 files)
Review ID: 035e49d6-6caa-4043-a768-8d6e2680fec7 Previous review (commit 5014fc3)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
WARNING
Files Reviewed (233 files)
Review ID: 035e49d6-6caa-4043-a768-8d6e2680fec7 Previous review (commit 83d2e1f)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
WARNING
Files Reviewed (233 files)
Review ID: 035e49d6-6caa-4043-a768-8d6e2680fec7 Previous reviewStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (233 files)
Review ID: ebd26ad0-2e2c-43d6-9557-ccbd6ee6659e Reviewed by ling-3.0-flash:free · Input: 98.2K · Output: 8.1K · Cached: 280.5K Review guidance: REVIEW.md from base branch |
Agents skip Spotless or panic when apply rewrites dozens of unrelated files. Root AGENTS.md now requires spotless:apply/check before every final PR commit (Java, docs, JS, TS), and mandates a separate "Spotless Cleanup" PR for formatting outside the task scope. > Co-Authored by Grok Build using grok-4.5 with agent Grok.
|
Follow-up commit
|
Addresses kilo-code-bot review on PR #1590. > Co-Authored by Grok Build using grok-4.5 with agent Grok.
Addresses kilo-code-bot CRITICAL/WARNING feedback on PR #1590: - docker/scripts/perc-devctl.py it-verify: pick mvnw vs mvnw.cmd by OS - scripts/release-audit/port.py verify_tests + spotless_check: same - scripts/verify-distribution-archive.py: restore accurate comment (bash avoided old mvn-env.sh, not the Maven wrapper) > Co-Authored by Grok Build using grok-4.5 with agent Grok.
…urrent targets Root and system agent docs still told agents to "use Java 17" or "Java 11+". development is release=21. Clarify: - development = JDK 21 only for new work - development-8.1.x = JDK 8 maintenance (unchanged) - Java 11/17 modernization checklists and CP-JAVA11 markers are historical - ai-shared-develop coding standards + Java 21 language instructions updated > Co-Authored by Grok Build using grok-4.5 with agent Grok.
building/overview/modernization/legacy/index/services still instructed "Modernize to Java 17". Align with release=21 baseline. > Co-Authored by Grok Build using grok-4.5 with agent Grok.
system/README.md remains relevant as the module map + build/agent guide, but the appended package modernization diary is gone. - Delete system/business/README.md (100% package log; no structure) - Delete servlet README + refactored-*.txt tracking lists - Replace services/ and webservices/ READMEs with short current guides - Point system/AGENTS.md away from deleted tracking files > Co-Authored by Grok Build using grok-4.5 with agent Grok.
|
Spotless honesty check (gate we just wrote — I had not run it before prior commits on this PR):
Cleanup PR: linked after create. |
|
Spotless cleanup PR for the 5 out-of-scope XMLs: #1591 |
Align system/services/README.md with sibling system READMEs and the cross-platform Maven wrapper docs standard (./mvnw / mvnw.cmd). Co-Authored by Grok Build using grok with agent pr-babysit.
Baseline Spotless rewrites outside PR #1590 (mvn-env / agent docs). Formatting-only; no product logic. > Co-Authored by Grok Build using grok-4.5 with agent Grok.
Summary
mvn-env.sh/mvn-env.bat(and the SC-004 sentinel that guarded them). Agents were routinely confused by dual wrapper paths and relative-path depth math../mvnw/mvnw.cmd.JAVA_HOME(the old wrappers rewroteJAVA_HOMEfromJAVA_HOME_21;mvnwdoes not).What changed
mvn-env.sh,mvn-env.bat,scripts/test_mvn_env_untouched.pymvnw/mvnw.cmdAGENTS.md,README.md,CONTRIBUTING.md,WINDOWS-BUILD-GUIDE.mdHow to build after this PR
Test plan
mvn-env.sh/mvn-env.batare gone from the branch tip./mvnw -vworks withJAVA_HOME→ JDK 21AGENTS.mdPre-PR section usesmvnwonlypython3 -m pytest docker/scripts/test_perc_devctl.py -q(stub now createsmvnw)Notes
test_mvn_env_untouchednotes updated so agents do not look for the deleted sentinel.