Hi all,
Playing back on GeoServer trunk I notice that logging has becoming quite messy again. I have noticed that there are a bunch of System.out.println statements around??
Also we seem to be spitting the contents of all the pages or resources around on the classpath? Multiple times. Its so much that it fills up my console buffer so I cant actually see any of the errors that are occuring during startup. Can someone please point me in the right direction to turn this off. Or at least turn the logging level down.
Thanks,
-Justin
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Hmmmm...
May I remind everyone of: http://docs.codehaus.org/display/GEOSDOC/3+Logging
We should _never_ be using any System.out calls. If you've committed code that uses it, please clean it up as soon as possible.
Chris
Justin Deoliveira wrote:
Hi all,
Playing back on GeoServer trunk I notice that logging has becoming quite messy again. I have noticed that there are a bunch of System.out.println statements around??
Also we seem to be spitting the contents of all the pages or resources around on the classpath? Multiple times. Its so much that it fills up my console buffer so I cant actually see any of the errors that are occuring during startup. Can someone please point me in the right direction to turn this off. Or at least turn the logging level down.
Thanks,
-Justin
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Hi all,
Playing back on GeoServer trunk I notice that logging has becoming quite messy again. I have noticed that there are a bunch of System.out.println statements around??
Indeed there are lots... Eclipse can find 100 of the in the Geoserver code...
Also we seem to be spitting the contents of all the pages or resources around on the classpath? Multiple times.
If you refer to all the functions and the like,
I think I've always seen Geoserver act like this, in fact I did increase the buffer size 50 times from the Eclipse default, so I have no recipe...
Cheers
Andrea
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
Playing back on GeoServer trunk I notice that logging has becoming quite messy again. I have noticed that there are a bunch of System.out.println statements around??
Indeed there are lots... Eclipse can find 100 of the in the Geoserver code...
Also we seem to be spitting the contents of all the pages or resources around on the classpath? Multiple times.
If you refer to all the functions and the like,
I think I've always seen Geoserver act like this, in fact I did increase the buffer size 50 times from the Eclipse default, so I have no recipe...
Hmmm, I am pretty sure this is something recent. When I was active in the release cycles last year I know for sure it didn't do this. I will see if I can hunt it down and kill it. Unless anyone has an objection?
Cheers
Andrea
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,45c8b4a175334750375898!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
The only println that I put in was for the data directory to print out, once, what the current running directory was at startup. I think I tried logging in it and it was acting weird. I can try changing it to a log again, but I don't think it is causing the log-barf, since it only executes once.
Brent Owens
(The Open Planning Project)
Chris Holmes wrote:
Hmmmm...
May I remind everyone of: http://docs.codehaus.org/display/GEOSDOC/3+Logging
We should _never_ be using any System.out calls. If you've committed code that uses it, please clean it up as soon as possible.
Chris
Justin Deoliveira wrote:
Hi all,
Playing back on GeoServer trunk I notice that logging has becoming quite messy again. I have noticed that there are a bunch of System.out.println statements around??
Also we seem to be spitting the contents of all the pages or resources around on the classpath? Multiple times. Its so much that it fills up my console buffer so I cant actually see any of the errors that are occuring during startup. Can someone please point me in the right direction to turn this off. Or at least turn the logging level down.
Thanks,
-Justin
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel