Changed those errors to warnings for logging since a default value is provided these are no real exceptions. Also set the unit test default log level to WARN
Let me know if this is ok, we could also keep them at error level and not provide the stack trace. I don't know of an option in log4j to hide the traces What do you think? On Tue, Jun 16, 2009 at 5:08 PM, Francis De Brabandere<[email protected]> wrote: > Hi Rainer, > > I'll have a look at the logging this evening. > > On Tue, Jun 16, 2009 at 5:03 PM, Rainer Döbele<[email protected]> wrote: >> Hi Francis (and everyone interested), >> >> after it has been very quiet on the dev-mailing list recently, I would like >> to revive the release process of empire-db 2.0.5 in order to be able to go >> ahead with some possibly bigger changes. >> >> The current assembly builds well and I as far as I can tell all required >> legal documents are there. >> However, there is one thing that annoys me: >> The JUnit test-code produces very verbose output - including some exceptions. >> Those exceptions are intended and handled properly - but are confusing. >> @Francis: is there a way of disabling log output when running the unit tests? >> >> Apart from that the assembly is fine to me. >> Anyone else to comment the assembly before we put it up for voting? >> >> Regards >> Rainer >> >> > > > > -- > http://www.somatik.be > Microsoft gives you windows, Linux gives you the whole house. > -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house.
