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 JDK 7 Travis build can be reproduced with:
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
Do not modernize away historical-JDK symptoms
When CI declares 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.
Build-repair artifact contract
This benchmark requires both a diagnosis artifact and an applicable patch. Before finishing:
- Create at least one non-empty standard unified diff at
/home/travis/build/failed/google/auto/patch_1.diff(or the repository path given by the task) containing the intended source/configuration change. - Apply that patch to the failed repository.
- Check
git diff/git statusand ensure the intended project file—not only the patch artifact—was changed. - Re-run the exact historical CI verification command under JDK 7.
- Do not finish until the full reactor, including Maven Invoker integration tests, succeeds.
Minimal diagnostic sequence
cd /home/travis/build/failed/google/auto
# 1. Establish target CI and toolchain.
sed -n '1,220p' .travis.yml
source /opt/jdk_switcher/jdk_switcher.sh
jdk_switcher use openjdk7
export TRAVIS_JDK_VERSION=openjdk7
java -version
mvn -version
# 2. Reproduce the real CI command.
mvn -Dhttps.protocols=TLSv1.2 -B -U -f build-pom.xml verify \
--fail-at-end -Dsource.skip=true -Dmaven.javadoc.skip=true
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