[ http://jira.codehaus.org/browse/MNG-399?page=all ]
Brett Porter updated MNG-399:
-----------------------------
Description:
It should be up to the plugin what log4j settings are used when the plugin is
executed. In this manner, a plugin could bundle two different log4j
configurations -- one for when the plugin was being operated normally, and the
other for debug (-X) mode. If there is no bundled configuration, the current
settings would be used.
This would be useful with the XDoclet plugin, because either it uses
nonstandard settings, or the settings that Maven chooses for it are
insufficient for error messages (which may be posted as warnings) to reach the
console. When this happens, generation problems are silently lost and the root
cause can be very difficult to track down.
was:
It should be up to the plugin what log4j settings are used when the plugin is
executed. In this manner, a plugin could bundle two different log4j
configurations -- one for when the plugin was being operated normally, and the
other for debug (-X) mode. If there is no bundled configuration, the current
settings would be used.
This would be useful with the XDoclet plugin, because either it uses
nonstandard settings, or the settings that Maven chooses for it are
insufficient for error messages (which may be posted as warnings) to reach the
console. When this happens, generation problems are silently lost and the root
cause can be very difficult to track down.
Fix Version: (was: 2.0-beta-4)
2.1
Environment:
> Per-plugin adjustable logging settings
> --------------------------------------
>
> Key: MNG-399
> URL: http://jira.codehaus.org/browse/MNG-399
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Reporter: Brian Topping
> Priority: Minor
> Fix For: 2.1
>
>
> It should be up to the plugin what log4j settings are used when the plugin is
> executed. In this manner, a plugin could bundle two different log4j
> configurations -- one for when the plugin was being operated normally, and
> the other for debug (-X) mode. If there is no bundled configuration, the
> current settings would be used.
> This would be useful with the XDoclet plugin, because either it uses
> nonstandard settings, or the settings that Maven chooses for it are
> insufficient for error messages (which may be posted as warnings) to reach
> the console. When this happens, generation problems are silently lost and
> the root cause can be very difficult to track down.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
