mojohaus / mojohaus/exec-maven-plugin
Modulepath lists dependencies in wrong order
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 191
- Forks
- 111
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 4
Description
Version 1.6.0
Testcase: https://github.com/cowwoc/maven-java9-class-shadowing
Repro steps:
- Project includes two dependencies A and B (in that specific order).
- A depends on C, where B and C contain the same package/class.
Expected behavior: the class in B should shadow the class in C.
Actual behavior: This plugin lists C on the modulepath before B, so C shadows B.
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 with the linked maven-java9-class-shadowing testcase and reproduce the modulepath ordering with dependencies A and B, where A depends on C. Trace the exec-maven-plugin code that assembles the modulepath. Done means B precedes C when their packages/classes overlap, with a regression test covering the dependency order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100