[
http://jira.codehaus.org/browse/MINVOKER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann reopened MINVOKER-66:
---------------------------------------
The implementation as is also suppresses logging of the artifact installer in
other plugins: I erroneously assumed the [instantiation
strategy|http://plexus.codehaus.org/ref/component-configuration.html] would be
per-lookup but is usually singleton. Even if the default weren't like this,
relying on such an assumption is a bad idea.
Either come up with up reliable/safe solution of revert it.
> Reduce log level for install goal output to debug
> -------------------------------------------------
>
> Key: MINVOKER-66
> URL: http://jira.codehaus.org/browse/MINVOKER-66
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.2.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 1.3
>
>
> The staging of artifacts to the test repo is currently logged with one
> message per file at info level. With the support for staging of all
> dependencies (MINVOKER-64) this heavily floods the console. We should try to
> grab the logger for the {{ArtifactInstaller}} and have it output its original
> INFO messages at DEBUG level to reduce the noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
