build: fail build explicitly on Javadoc errors#24330
Draft
Artur- wants to merge 4 commits into
Draft
Conversation
Make failOnError explicit on maven-javadoc-plugin so Javadoc errors visibly break the build instead of being buried in log output.
Test Results1 283 files - 123 1 283 suites - 123 1h 18m 34s ⏱️ - 4m 22s Results for commit 62ee2a2. ± Comparison against base commit 8f15084. ♻️ This comment has been updated with latest results. |
Maven prefixes every Javadoc tool stderr line with [ERROR], so the single real "error:" line gets lost among 100+ identically-prefixed warning lines. Extract the actual error lines from the Maven log and write them to GITHUB_STEP_SUMMARY so they're visible directly on the PR check page.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.