Hi devs, I’m curious about the occasional use of java.util.logging in Tika:
> ./tika-core/src/main/java/org/apache/tika/config/InitializableProblemHandler.java:import > java.util.logging.Logger; > ./tika-core/src/main/java/org/apache/tika/config/LoadErrorHandler.java:import > java.util.logging.Logger; > ./tika-core/src/main/java/org/apache/tika/detect/NNExampleModelDetector.java:import > java.util.logging.Logger; > ./tika-core/src/main/java/org/apache/tika/utils/XMLReaderUtils.java:import > java.util.logging.Logger; > ./tika-nlp/src/main/java/org/apache/tika/parser/recognition/AgeRecogniser.java:import > java.util.logging.Logger; Most (all?) of the other Tika code is using slf4j. I noticed this when my well-formatted log file suddenly contained this entry (no timestamp, etc) > Jan 31, 2018 1:28:21 PM org.apache.tika.config.InitializableProblemHandler$3 > handleInitializableProblem > WARNING: org.xerial's sqlite-jdbc is not loaded. > Please provide the jar on your classpath to parse sqlite files. > See tika-parsers/pom.xml for the correct version. Were these uses of java.util.logging intentional? Thanks, — Ken -------------------------------------------- http://about.me/kkrugler +1 530-210-6378
