fbiville / fbiville/mvn-plugin-dependency-reactor-issue
Wrong reproducer
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is simply wrong reproducer, what it tries to do is wrong, here is why:
Let's examine the mvn -am -pl plugin-dependency,a-module more obvious case. Am stating the "obvious" (maven console output) in order it happens with explanations:
- Maven topologically sorts the projects it is about to build, console states:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Parent POM [pom]
[INFO] A plugin dependency [jar]
[INFO] A module [jar]
Hence, we see the order is: mvn-plugin-dependency-reactor-issue (parent), plugin-dependency and a-module.
- First parent is being built:
[INFO]
[INFO] ------------< com.acme:mvn-plugin-dependency-reactor-issue >------------
[INFO] Building Parent POM 1.0-SNAPSHOT [1/3]
[INFO] --------------------------------[ pom ]---------------------------------
- Build would invoke checkstyle:check goal on parent:
[INFO]
[INFO] --- maven-checkstyle-plugin:3.1.2:check (default-cli) @ mvn-plugin-dependency-reactor-issue ---
- Errors out with message:
Execution default-cli of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2 or one of its dependencies could not be resolved
As expected, as plugin-dependency (used as dependency for check-style plugin) is NOT YET BUILT. As we saw above, it was planned to be built AFTER parent. But to build parent, it needs plugin-dependency, but to build plugin-dependency, it needs parent to be built....
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running mvn -am -pl plugin-dependency,a-module and reviewing the reported reactor build order and checkstyle failure. No source file or test is named, and the issue does not define a concrete change or acceptance condition, so the intended outcome needs clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100