forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Siveton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FOR-1025) [forrestdoc] Improve debugging stuff with log4j or otherwise
Date Wed, 11 Jul 2007 04:05:04 GMT

     [ 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.


Mime
View raw message