apache / apache/maven-dependency-plugin
[MDEP-879] Wanted: analyze-report-only goal
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Karsten Spang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kspang_impala_76b0)** opened **[MDEP-879](https://issues.apache.org/jira/browse/MDEP-879?redirect=false)** and commented
I would like to have a report goal that does not trigger test-compile.
I have several projects using generated sources. Since the sources are re-generated before the compile step, the compiler plugin does not skip over code already compiled. This takes unnecessary time when running `mvn clean verify site`.
---
No further details from [MDEP-879](https://issues.apache.org/jira/browse/MDEP-879?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Maven Dependency Plugin implementation of the report goal and its tests; the issue names no files or test entry points. Trace why the report goal triggers test-compile, then determine how a report-only goal would avoid that step while still producing the dependency report. Done means the requested goal works for projects with generated sources and has coverage for the no-test-compile behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100