[jira] Moved: (MNG-399) Per-plugin adjustable log4j settings

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-399?page=all ]

Brett Porter moved MAVEN-1145 to MNG-399:
-----------------------------------------

    Fix Version: 2.0-beta-1
      Component:     (was: plugin manager)
                 maven-core
     Issue Type: Bug  (was: Improvement)
            Key: MNG-399  (was: MAVEN-1145)
        Project: m2  (was: maven)

> Per-plugin adjustable log4j settings
> ------------------------------------
>
>          Key: MNG-399
>          URL: http://jira.codehaus.org/browse/MNG-399
>      Project: m2
>         Type: Bug
>   Components: maven-core
>     Reporter: Brian Topping
>      Fix For: 2.0-beta-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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org