[
https://issues.apache.org/jira/browse/MTOMCAT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461653#comment-13461653
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-176:
------------------------------------------------
You must have a look at TomcatManager class there is an inner class called
RequestEntityImplementation.
See the method: transferProgressed.
An idea could be to passed the batchMode flag from mojos to the class to write
or not the status.
> Make deploy/redeploy (upload) less verbose for --batch-mode / --quiet
> ---------------------------------------------------------------------
>
> Key: MTOMCAT-176
> URL: https://issues.apache.org/jira/browse/MTOMCAT-176
> Project: Apache Tomcat Maven Plugin
> Issue Type: Wish
> Components: commons-lib
> Affects Versions: 2.0
> Reporter: Thomas GL
> Assignee: Olivier Lamy (*$^¨%`£)
> Priority: Minor
>
> Hi,
> Using maven-tomcat-plugin:2.0 for integration testing deployments results in
> some Jenkins job logs where 99% of the lines comes from the upload "progress
> meter" (implemented in
> "TomcatManager.RequestEntityImplementation.transferProgressed").
> In some other plugins with similar HTTP activity, this kind of output can be
> turned off by launching Maven with "-B/--batch-mode" (and probably "--quiet"
> too, although I never do that). This seems to be standard behavior for
> plugins which uses Wagon or Aether. Would it be possible to implement a
> similar behavior in the maven-tomcat-plugin?
> Actually, I gave it a try today, but I couldn't find how to get the Maven
> batch/quiet options through the plugin API. My other attempt was to reuse
> the Wagon "TransferListener" instance (the implementation, which can be a
> verbose or quiet progress meter, seems to be chosen depending on the Maven
> CLI option), but I couldn't find a path to there neither. But it's my first
> time in some Maven code, I probably have missed something.
> Sure, if it's actually not possible to implement a quiet mode based on the
> Maven CLI options, then an alternative would be to add a plugin-specific
> parameter. But I think it would be a bit less convenient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
