You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/06/01 05:32:58 UTC
[jira] Closed: (MNG-2554) Maven 2.1 trunk does not activate debug
logging with the -X/--debug command line options.
[ http://jira.codehaus.org/browse/MNG-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2554.
------------------------------
Resolution: Fixed
It now produces lots of debug logging!
> Maven 2.1 trunk does not activate debug logging with the -X/--debug command line options.
> -----------------------------------------------------------------------------------------
>
> Key: MNG-2554
> URL: http://jira.codehaus.org/browse/MNG-2554
> Project: Maven 2
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.0.4
> Reporter: Binyan
> Attachments: MNG-2554-maven-core.patch
>
>
> It is not possible to get the maven 2.1 source on the trunk to produce debug output. The reason is because the mojo logger instance does not have its threshold logging level updated from info to debug in the request passed to the Maven.execute() method.
--
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