This repository was archived by the owner on Jun 2, 2019. It is now read-only.
Run maven in batch mode to prevent log spam #51
Merged
Conversation
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
carlossg
added a commit
that referenced
this pull request
Feb 3, 2016
Run maven in batch mode to prevent log spam
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Maven is run in interactive mode, which means when downloading a large artifact, maven will print out how far through the download it is (e.g.
172Kb/1651Kb) and constantly updates this value in the console. The maven output appears in the puppet output if--debugis used. However, this means if capturing the logs of a puppet apply, you may have many many lines of output from maven just keeping its xKb/yKb updated.This PR sets maven to batch mode, to stop it printing out these kind of logs.