Well, I can only speak for me - I'll let others chime in as to how they like to work.
Maybe I'm in a minority, I don't know.
When I'm developing, I'm running "standalone.sh" and watching the
console. I like to see my DEBUG msgs on the console. If we only do it for log files, then
I'm forced to run standalone.sh in background (or run it in another command line
window) and then tail the log file. Extra steps I have to do for each run of my server
that I would prefer not to do.
So to recap, before yesterday, I would do:
standalone.sh
If we keep with the standalone-itest.xml and only put debug msgs in log files, I would
do:
standalone.sh -c standalone-itest.xml &
tail -f ../standalone/log/server.log
I like just running "standalone.sh" :)
----- Original Message -----
On 28 May 2015, at 22:28, John Mazzitelli wrote:
> The CONSOLE needs to be at DEBUG because without that, it doesn't
> matter what you do to the individual categories, the debug messages
> get eaten up. changing the CONSOLE level to DEBUG was just yet
Could we put the DEBUG level only for the *log file* (and make it wrap
over only at large log sizes) and keep the (stdout) console at INFO
level?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev