kulukimak / dkpro-core-asl

Automatically exported from code.google.com/p/dkpro-core-asl
0 stars 0 forks source link

ResourceObjectProviderBase logs too verbosely #488

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
In my application where I instantiate various annotators several times 
(https://github.com/brmson/yodaqa), ResourceObjectProviderBase is producing 
many INFO-level messages that repeat like this:

INFO ResourceObjectProviderBase - :: loading settings :: url = 
jar:file:/home/pasky/.m2/repository/org/apache/ivy/ivy/2.3.0/ivy-2.3.0.jar!/org/
apache/ivy/core/settings/ivysettings.xml
INFO ResourceObjectProviderBase - :: loading settings :: url = 
jar:file:/home/pasky/.m2/repository/org/apache/ivy/ivy/2.3.0/ivy-2.3.0.jar!/org/
apache/ivy/core/settings/ivysettings.xml
INFO ResourceObjectProviderBase - Producing resource from 
[jar:file:/home/pasky/.ivy2/cache/de.tudarmstadt.ukp.dkpro.core/de.tudarmstadt.u
kp.dkpro.core.opennlp-upstream-sentence-en-maxent/jars/de.tudarmstadt.ukp.dkpro.
core.opennlp-upstream-sentence-en-maxent-20120616.jar!/de/tudarmstadt/ukp/dkpro/
core/opennlp/lib/sentence-en-maxent.bin] redirected from 
[jar:file:/home/pasky/.ivy2/cache/de.tudarmstadt.ukp.dkpro.core/de.tudarmstadt.u
kp.dkpro.core.opennlp-model-sentence-en-maxent/jars/de.tudarmstadt.ukp.dkpro.cor
e.opennlp-model-sentence-en-maxent-20120616.1.jar!/de/tudarmstadt/ukp/dkpro/core
/opennlp/lib/sentence-en-maxent.properties]
INFO ResourceObjectProviderBase - Producing resource took 167ms

I believe at least the ":: loading settings ::" should be DEBUG-level instead 
since normally they aren't interesting to the user at all.

Regarding the latter two, I think it would be user-friendlier to move them to 
DEBUG and possibly produce a single and much shorter post-load INFO message 
"Producing resource 
/de/tudarmstadt/ukp/dkpro/core/opennlp/lib/sentence-en-maxent.bin took 167ms", 
but if you say that users not interested in this should just bump dkpro log 
level to WARN, that's fine too.

Original issue reported on code.google.com by pa...@ucw.cz on 3 Oct 2014 at 10:31

GoogleCodeExporter commented 9 years ago
We are not logging this directly, we just forward logging messages created by 
Ivy through Apache Commons Logging.

Original comment by richard.eckart on 4 Oct 2014 at 6:30