There is more to it than just setting system properties,
and I don't start eclipse from the command line anyway.
I also want to be able run tests and see the logging in the console.
It's inefficient in my opinion to have to shell out to a file to inspect the logging.
e.g. can't click on a stacktrace and go straight to the line of code that caused the
problem.
As I've said, it should be Hudson or Maven that redirects logging to a file
using the log4j.configuration system property.
It shouldn't automatically go there using hardwired rules embedded in the change log
that are not suitable for everybody's working practices.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266351#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...