Hi, > Stefan, >> ... I have used Log4j before, >> and it seemed a little complicated. > I find the log4j.properties variant complicated as well. But the > log4j.xml [1] configuration variant I find fairly straight forward [2]. > I can include/exclude log messages from particular java packages and log > priorities. In my developments, I tend to prefer java logging api because my needs are very basic and it avoids a dependency, but I know that experimented developpers find log4j (or maybe slf4j) better for some reasons...
By the way, it is not the high to the day to change, and I agree that system.out.println should be removed from svn code, even if I often use it for debugging purpose during early development phases. Kevin, I think you can feel free to replace system.out.println by logging statements. At least this is my opinion. Maybe there are some places where it would be even better to remove the system.out.println code (in that case, it could be discussed with the original author). I suppose there is a way to redirect logging outputs to the console if one prefer seeing messages in the console during development. my 2 cents Michaël >> I wonder if just having the >> ability to write messages to a simple plain-text log file would >> suffice. >> > Which is one of many output appenders available to log4j :) I agree, > this is what I would recommend. From user's perspective, one can submit > the log file when posting a bug report. We can even include a parameter > in the JUMP launcher that would temporarily set the log priority to > debug or even verbose to help with bug reports. > > My 2 cents, > -- Kevin > > > [1] http://wiki.apache.org/logging-log4j/Log4jXmlFormat > [2] http://wiki.apache.org/logging-log4j/Log4jXmlFormat#Example_2 > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
