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 and flags:
# Example only — replace `-f ...` and flags with the repository's CI command.
mvn -Dhttps.protocols=TLSv1.2 -B -U -f <reactor-pom.xml> verify --fail-at-end
Maven Invoker integration tests (nested projects)
Some Maven builds run integration tests via maven-invoker-plugin (often during
verify). These tests execute Maven in nested sample projects (commonly under
src/it/**), which changes how you should interpret dependency failures.
Key implications:
- Dependency resolution is scoped to the nested project.
dependencyManagement,pluginManagement, and<repositories>from the main build do not apply unless the nested project'spom.xmlexplicitly inherits them. - Invoker runs may use an isolated local repository under
target/**. A missing artifact can mean it was never installed into the invoker repo, not that the main reactor failed to build it.
When a nested project fails to resolve an artifact/plugin:
- Identify which invoker project failed (from CI logs or
target/invoker-reports/). - Inspect the source-controlled template under
src/it/...and any invokersettings.xml/invoker.propertiesused for those runs. - Check the invoker configuration in the real build POM for how it seeds the local
repo (e.g.
invoker:install,installArtifacts, setup goals) and which settings file/repositories it uses.
To iterate faster, many invoker setups support running a single project and streaming logs, for example:
mvn -pl <module-running-invoker> -Dinvoker.test=<project-pattern> -Dinvoker.streamLogs=true verify
Modification scope rule for invoker tests:
- Never edit
target/**(cloned test projects, invoker local repositories, or generated reports). Those directories are regenerated; fixes must be made in the real module POM(s) and/or undersrc/it/**templates so they are captured in patches and version control.
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:
- Write your diagnosis and plan to the task-specified notes file (commonly
/home/travis/build/failed/failed_reasons.txt). - Create at least one non-empty standard unified diff at the task-specified patch
path (commonly
<repo_path>/patch_1.diff) 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 CI verification command under the CI-declared toolchain/JDK.
- Do not finish until the full reactor, including Maven Invoker integration tests, succeeds.
Minimal diagnostic sequence
REPO=/home/travis/build/failed/<repo>/<id>
cd "$REPO"
# 1. Establish target CI and toolchain.
sed -n '1,220p' .travis.yml
java -version
javac -version
mvn -version
# If CI declares a specific JDK and a switcher is available, switch first.
if [ -f /opt/jdk_switcher/jdk_switcher.sh ]; then
source /opt/jdk_switcher/jdk_switcher.sh
jdk_switcher use <ci-jdk> # e.g., openjdk7
export TRAVIS_JDK_VERSION=<ci-jdk>
fi
java -version
# 2. Reproduce the real CI command (replace with the actual command/flags).
mvn -B -U -f <reactor-pom.xml> verify --fail-at-end
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