You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Vincent Siveton (JIRA)" <ji...@apache.org> on 2007/07/10 15:43:04 UTC
[jira] Created: (FOR-1025) [forrestdoc] Improve debugging stuff
with log4j or otherwise
[forrestdoc] Improve debugging stuff with log4j or otherwise
-------------------------------------------------------------
Key: FOR-1025
URL: https://issues.apache.org/jira/browse/FOR-1025
Project: Forrest
Issue Type: Improvement
Components: Tool: Forrestdoc
Reporter: Vincent Siveton
The forrestdoc code has:
* custom debug flags to provide Systom.out.print() trace or new Exception().printStackTrace().
* some printStacktrace() in catch Exception
I propose to use log4j instead of.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FOR-1025) [forrestdoc] Improve debugging stuff
with log4j or otherwise
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thorsten Scherler closed FOR-1025.
----------------------------------
Resolution: Fixed
Committed revision 556752.
> [forrestdoc] Improve debugging stuff with log4j or otherwise
> -------------------------------------------------------------
>
> Key: FOR-1025
> URL: https://issues.apache.org/jira/browse/FOR-1025
> Project: Forrest
> Issue Type: Improvement
> Components: Tool: Forrestdoc
> Reporter: Vincent Siveton
> Attachments: FOR-1025.patch, log4j.properties
>
>
> The forrestdoc code has:
> * custom debug flags to provide Systom.out.print() trace or new Exception().printStackTrace().
> * some printStacktrace() in catch Exception
> I propose to use log4j instead of.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1025) [forrestdoc] Improve debugging stuff
with log4j or otherwise
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton updated FOR-1025:
---------------------------------
Attachment: log4j.properties
FOR-1025.patch
These patches provide:
* added debug stuff with log4j, special thanks to log4e ;)
* replaced commented debug stuff (prefer to removed)
* log4j conf file
* updated some javadoc fields
* removed used fields
* added some serialVersionUID
* fixed FOR-1026
*Note:* you need to update the build.xml file to add the log4j jar ,something like:
{noformat}
<path id="lib.classpath">
...
<fileset dir="${basedir}/../../lib/core">
<include name="log4j-1.2.13.jar" />
</fileset>
...
</path>
{noformat}
> [forrestdoc] Improve debugging stuff with log4j or otherwise
> -------------------------------------------------------------
>
> Key: FOR-1025
> URL: https://issues.apache.org/jira/browse/FOR-1025
> Project: Forrest
> Issue Type: Improvement
> Components: Tool: Forrestdoc
> Reporter: Vincent Siveton
> Attachments: FOR-1025.patch, log4j.properties
>
>
> The forrestdoc code has:
> * custom debug flags to provide Systom.out.print() trace or new Exception().printStackTrace().
> * some printStacktrace() in catch Exception
> I propose to use log4j instead of.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.