So, I don't know (yet) about 1), and 2) would usually work by configuring Jetty's logging itself. I have looked at configuring logging with Jetty directly (e.g. by adjusting etc/commons-logging.properties) but that didn't work.
I'm a bit short on time here, but I'll try to look futher into it tommorrow. If you come with new conclusions, they are welcome :)
Regards,
Eelco
Andreas Andreou wrote:
Hi,
thanks for the interest...
I too am using commons-logging with log4j.
However, bizzare things happen:
on jetty launch (from within eclipse)
the log file (defined in log4j.properties) is created,
but then nothing is appended to it, nor to the console.
Instead, at the console I get many messages from jetty's logger
the first one being
INFO [main] org.mortbay.log.LogImpl.add(LogImpl.java:109)
I wouldn't mind with that, but this logger runs at the INFO level
and not at the DEBUG, so i can't see my (debug) messages there...
So, to recap:
1) Jetty's logger seems to pop in, in place of commons-logging
2) There isn't an easy way to configure jetty's logger to the debug level
(at least without having to write a custom jetty.xml and use that in the launcher)
Any ideas?
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Jettylauncher-plugin mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jettylauncher-plugin
