apache / apache/maven-javadoc-plugin
[MJAVADOC-735] Analyze javadoc output and output individual log statements for warning and errors
- Dominant language
- Java
- Stars
- 107
- Forks
- 116
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
**[Guillaume Nodet](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gnt)** opened **[MJAVADOC-735](https://issues.apache.org/jira/browse/MJAVADOC-735?redirect=false)** and commented
When a javadoc fails, the few errors can be very difficult to find inside the maven log when there are a lot of warnings. In particular, all warnings are then displayed as errors and it is very unintuitive that a few errors cause the problem.
---
No further details from [MJAVADOC-735](https://issues.apache.org/jira/browse/MJAVADOC-735?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing how the Maven Javadoc Plugin reports Javadoc warnings and errors, then identify existing logging tests before defining what separate warning and error output should look like.
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