From: Bertrand F. <ber...@fl...> - 2008-07-25 13:53:39
|
Thanks Paul, it worked. (Thanks to Sylvain as well for your tip from atunes.) PaulTaylor wrote: > Bertrand Florat wrote: >> To sum up what I think and learn on big projects is that a library >> should avoid to impose external configuration (like properties file) >> but should pop it from its environment. Imagine the mess when your >> app makes use of tens of libs and if each comes with a different >> approach to configure it (one with an XML file, another with a >> property file, another with... wait : the same properties file that >> collide with the previous one ...). It's even more important for logs >> because it's very convenient to have a single file to configure all >> libs but also to get all logs in the same format and in the same files. > Yeah, but Im not introducing any new properties file at all, Im using > the logging built into Java, if every library took the same approach > we wouldnt have a problem. > >> >> Could you please detail the procedure to totally disable logs for >> jaudiotagger ? I suppose we need a logging.properties file in the >> classpath but which keys should we change or drop ? >> > Its very simple just add org.jaudiotagger.level = OFF > > You can put this in logging.properties in your JRE lib folder > OR you use the -Djava.util.logging.config.file to specify your own > properties file. > OR you create a Properties object in your code and then use > LogManager.getLogManager().readConfiguration(); to read the settings > from this > > > Paul > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev...@ja... > For additional commands, e-mail: dev...@ja... > > -- Bertrand FLORAT ber...@fl... http://www.florat.net Chat: bf...@ja... PGP keyserver: pgp.mit.edu Try Jajuk Advanced jukebox (http://jajuk.info) |