On 12/10/10 17:01, Andrea Aime wrote: > Yeah, java logging is quite lame config wise. Have a look at: > modules/library/jdbc/src/test/java/org/geotools/jdbc/JDBCTestSupport.java > That class has programmatic logging setup that we uncomment when we really > need logging going. Maybe not the perfect solution, but proved to be useful > in more than one occasion (thanks Justin for setting it up)
Thanks Andrea. I used even nastier tricks in gt-app-schema-resolver AppSchemaConfigurationTest, but I was wondering if there was a better way? It seems to me that test logging should be configurable from outside the code, by setting a property (or even many). Justin's solution seems a bit cleaner; I ended up hacking the root logger to log everything. Logging is not very test-friendly, and I end up scattering System.err breadcrumbs in code, which is a logging antipattern. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
