The Travis logs were once again too long. A major culprit of log length is progress updates when downloading external maven packages.
This change enables batch mode on the site generation (it was already enabled on the main mvn install). Batch mode will eliminate these progress updates from our log and hopefully will make it short enough.
How was it tested?
The Progress updates themselves don't actually print to terminal when we are developing locally, but you can see them flash up on the bottom of the screen. Before the change I could see them briefly but after the change I couldn't see them at all.
Also, the fact that when the mvn install command runs (with the batch option enabled) there are none of these progress updates in the output provided me with more confidence that I was making the right change.
What was changed? Why is this necessary?
The Travis logs were once again too long. A major culprit of log length is progress updates when downloading external maven packages.
This change enables batch mode on the site generation (it was already enabled on the main mvn install). Batch mode will eliminate these progress updates from our log and hopefully will make it short enough.
How was it tested?
The Progress updates themselves don't actually print to terminal when we are developing locally, but you can see them flash up on the bottom of the screen. Before the change I could see them briefly but after the change I couldn't see them at all.
Also, the fact that when the
mvn installcommand runs (with the batch option enabled) there are none of these progress updates in the output provided me with more confidence that I was making the right change.How to test
./mvnw clean install -U