maven-build-lifecycle
Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- maven-build-lifecycle
- description
- Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.
03 SKILL.md 正文
Maven Build Lifecycle — Legacy CI Repair Workflow
Core rule: reproduce the target CI before changing the project
For build-repair tasks, the first successful local command is not enough. The
failure must be reproduced under the toolchain and Maven command used by the
target CI. Read the repository's CI configuration (.travis.yml, workflow
files, wrapper scripts, build POMs) before interpreting any compiler or
dependency error.
Record at least:
java -version
javac -version
mvn -version
If the repository declares a historical JDK and the container's default Java is newer, switch to the declared JDK before patching project files. A failure caused only by running an old project on a modern JDK is not evidence that the project should be migrated.
For environments that provide the BugSwarm JDK switcher, a Travis build that pins an older JDK can be reproduced with (example for JDK 7):
source /opt/jdk_switcher/jdk_switcher.sh
jdk_switcher use openjdk7
export TRAVIS_JDK_VERSION=openjdk7
java -version
Then run the exact CI build command, including any non-default reactor POM:
mvn -Dhttps.protocols=TLSv1.2 -B -U -f build-pom.xml verify \
--fail-at-end -Dsource.skip=true -Dmaven.javadoc.skip=true
Maven Invoker / nested test projects: fix the template POMs, not generated copies
If the build fails while running Maven Invoker (or any integration test that builds “nested projects”), treat those nested projects as real builds with their own dependency resolution:
- Identify where the nested projects are sourced from (commonly
src/it/**,src/test/resources/**, or a dedicatedit/directory). - Identify the failing nested project directory from the Maven output (Invoker
commonly runs builds under
target/**). Then map it back to the source template under the repository (e.g.,src/it/<case>/pom.xml). - Apply dependency/plugin/version fixes to the source templates under the
repository, not to generated directories under
target/**(those will be recreated on every run). - Before deciding “fix root POM vs nested POM”, inspect the nested project’s
pom.xmlparent chain:- If the nested
pom.xmldoes not inherit the reactor’sdependencyManagement/pluginManagement(no parent relationship to your reactor POM), then fixes must live in the nested templatepom.xml(or a parent POM within that template project), because the invoker build won’t see reactor-managed versions. - If the nested
pom.xmldoes inherit from a parent POM in the repository, apply fixes to the parent so the nested project resolves the change naturally.
- If the nested
- If invoker projects fail to resolve artifacts, distinguish plugin resolution failures vs normal dependency failures; nested builds may require their own plugin versions/repositories if they don’t inherit yours.
Do not modernize away historical-JDK symptoms
When CI declares an old JDK (e.g., JDK 7), do not respond to a default-JDK-11 failure by blindly doing any of the following:
- changing Java source/target solely to make the project compile on Java 11;
- removing or excluding
com.sun:tools/tools.jarsolely because Java 9+ no longer ships it; - adding replacement annotation APIs solely for
javax.annotation.Generated; - changing production logic because javac's post-Java-8 module model produces different compiler-element behavior.
First reproduce on the declared JDK. Only errors that remain under the target
CI environment should drive the repair. (Conversely, if CI is already on Java 9+,
then tools.jar/system-scope issues are genuine build breakages to fix.)
Build-repair artifact contract (must satisfy for evaluation)
This benchmark requires both a diagnosis artifact and an applicable patch. Create these artifacts early (immediately after you have a reproducible failure), not at the end.
- Write a non-empty diagnosis + plan to:
/home/travis/build/failed/failed_reasons.txt - Create at least one non-empty unified diff at:
/home/travis/build/failed/<repo>/<id>/patch_1.diff(incrementpatch_{i}.diffif you need multiple patches)- Prefer generating patches via
git diff > patch_1.diffso you don’t have to hand-author multi-line diff content.
- Prefer generating patches via
- Ensure the repository working tree actually reflects the patch (not only the
patch artifact):
- verify with
git statusandgit diff --stat - if you generated the patch from local edits, prove the patch is usable by
resetting tracked files and re-applying it:
git checkout -- .(orgit reset --hard) thengit apply patch_1.diff
- verify with
- Re-run the exact CI verification command (same JDK, same Maven flags, same reactor POM) until it succeeds, including any Maven Invoker integration tests.
Minimal diagnostic sequence (run each command separately)
The execution tool in this environment may reject multi-line / multi-command blocks; run commands one-at-a-time.
-
Locate and enter the repository’s concrete
<repo>/<id>directory under/home/travis/build/failed(do not stop at the org/namespace or repo directory; you must reach the final build workspace that contains the POMs):cd /home/travis/build/failedls -lals -la /home/travis/build/failed/<namespace-or-owner>ls -la /home/travis/build/failed/<namespace-or-owner>/<repo-name>cd /home/travis/build/failed/<namespace-or-owner>/<repo-name>/<id>pwdls -la(Confirm you’re in the right place by seeing project files such as
.travis.yml,pom.xml,mvnw, or module directories.) -
Inspect CI config to find the real build command and JDK:
sed -n '1,220p' .travis.yml -
Record tool versions (paste these into
failed_reasons.txt):java -versionjavac -versionmvn -version -
Reproduce the failure with the CI command. If the environment is offline or dependencies are expected to come from the local cache, also try an offline run to get actionable “missing artifact/plugin” coordinates:
mvn -o -B -e verify --fail-at-end -
Locate the source of the error:
- For missing artifact/plugin coordinates: check whether it’s a build plugin resolution issue vs a normal dependency issue (plugins resolve too).
- For “file not found” /
systemPathbreakage: grep the repository for the failing coordinate/path string (e.g.,tools.jar). - If you suspect offline-cache gaps, confirm what is and isn’t present under
~/.m2/repository/to narrow the failure. - If the failure happens in a nested/Invoker build under
target/**, locate the corresponding source template project undersrc/it/**(or equivalent) and plan to modify that template, not the generated copy.
-
Immediately write/update the required diagnosis+plan file (do this before you start editing files for the fix):
- Use a one-liner write so you don’t need multi-line shell blocks:
printf '%s\n' \ "Repro command: <paste exact mvn command>" \ "Observed failure: <paste key Maven error lines>" \ "Root cause guess: <code vs build config?>" \ "Plan: <files to change + why>" \ > /home/travis/build/failed/failed_reasons.txt - Verify it exists and is non-empty:
test -s /home/travis/build/failed/failed_reasons.txt && echo "notes ok"
- Use a one-liner write so you don’t need multi-line shell blocks:
General Maven lifecycle reminders
mvn testdoes not imply thatmvn verifypasses.verifycan execute integration-test and Invoker steps thattestnever reaches.- A green command run under the wrong JDK is not sufficient evidence of a valid CI repair.
04 同仓库更多 Skills
video-frame-extraction
Extract frames from video files and save them as images using OpenCV
openai-vision
Analyze images and multi-frame sequences using OpenAI GPT vision models
image-ocr
Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms
video-frame-extraction
Extract frames from video files and save them as images using OpenCV
openai-vision
Analyze images and multi-frame sequences using OpenAI GPT vision models
image-ocr
Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms