This repository has been archived by the owner on Apr 28, 2023. It is now read-only.
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.
Right now it is impossible to debug most build errors because Maven is run in interactive mode, which spams thousands of lines of progress indicators into the log file.
This makes it really hard to find the problematic lines as it is but even worse is that Docker BuildKit will limit log size to 1 MB at which point it just stops logging.
While there are in theory options to increase log size, those did not work in my testing and also the far better fix is to correctly set Maven to batch mode, which is intended for noninteractive use like Docker and GitHub actions.
Also, this pull request sets the Maven transfer log level to warn, so that lines like "Downloading from X: Y" are hidden unless there is a problem.
For example, currently, just one single dependency, jcl-over-slf4j, causes the output shown below (note that it scrolls far to the right).
Attached to this PR are also the log files from before (clipped at 1 MB) and after (136 k).