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).
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).