maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Topping (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-399) Per-plugin adjustable logging settings
Date Tue, 24 Oct 2006 20:05:39 GMT
     [ http://jira.codehaus.org/browse/MNG-399?page=all ]

Brian Topping closed MNG-399.
-----------------------------

    Resolution: Fixed

> Per-plugin adjustable logging settings
> --------------------------------------
>
>                 Key: MNG-399
>                 URL: http://jira.codehaus.org/browse/MNG-399
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>            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

        

Mime
View raw message