[ 
https://jira.codehaus.org/browse/MNG-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356241#comment-356241
 ] 

Michael Osipov commented on MNG-5486:
-------------------------------------

Are we good to close this one? The GitHub PR has been closed too.

> hiding transfer logs
> --------------------
>
>                 Key: MNG-5486
>                 URL: https://jira.codehaus.org/browse/MNG-5486
>             Project: Maven
>          Issue Type: Improvement
>          Components: Command Line, Embedding, Logging, Performance
>    Affects Versions: 3.0.5, 3.1.0
>            Reporter: Jigar Joshi
>            Priority: Minor
>         Attachments: maven_qtl.patch, maven_qtl.patch, maven_qtl.patch
>
>
> Maven {{ConsoleMavenTransferListener}} adds too much verbose logs, Which is 
> not required in all the cases and most of the time people uses it ( 
> {{ConsoleMavenTransferListener}} by default)
> It causes little overhead,
> For example: in CI build it adds those logs which is not required all the 
> time, also (in my case) it triggers the build of a very large maven project 
> tree at each 10 min adding lots of logs on disk
> Also there are other people who wants this feature as well
> http://maven.40175.n5.nabble.com/m2-Turning-off-download-log-messages-td46662.html
> http://stackoverflow.com/questions/3409918/maven-how-can-i-stop-the-deploy-plugin-from-logging-upload-progress
> I know there is a {{-q}} but which gets very quiet, so it would be nice if we 
> are able to just quiet transfer logs
> I modified maven source to hide those log based on the parameter and using it 
> successfully
> I have attached the patch here which was applied against 3.1-SNAPSHOT 
> specifically at revision : 1495788
> https://svn.apache.org/repos/asf/maven/maven-3/trunk
> added new parameter
> {{-qtl}}
> to make quiet transfer log
> If I overlooked anything and did over engineering please let me know,
> Otherwise I would love to see this option in next release
> Thanks!
> Jigar



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to