Any removal of System.out is a Good Thing.
To customise log4j, you must override log4j.properties in maven.jar using the standard log4j initialisation technique (eg -Dlog4j.properties=...)
- Brett
Eric Pugh wrote:
Hi all,
the jxr plugin is dumping lots of these messages:
PackageManager -> parsing... com\upstate\commons\turbine\om\BaseObject.java PackageManager -> parsing... com\upstate\commons\turbine\pulltool\CustomerTool.java PackageManager -> parsing... com\upstate\commons\turbine\pulltool\FormatTool.java PackageManager -> parsing... com\upstate\commons\turbine\pulltool\SessionPageData.java
I thought that maybe this was because I had a log4j.properties file in my path, and it was being picked up.. But, I can't seem to turn it off. I added
log4j.category.org.apache.maven.jxr.pacman.PackageManager=WARN
to try.. To customize logging, do I need to put a log4j.properties in my MAVEN_HOME/libs directory?
Related, there seems to be a bunch of out of date methods etc in JXR.. Anyone mind if I remove the extra unused logging methods like one that does System.out.println?
Argh, Eric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
