[
https://issues.apache.org/jira/browse/TIKA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971103#action_12971103
]
Nick Burch commented on TIKA-571:
---------------------------------
The wrong netcdf jar ended up in maven, see TIKA-556 for details
Until the next Tika release is out, if this affects you, please just tweak the
dependency in the Tika pom
> A Tika dependency contains a logging adapter, which overrides attempts to
> specify your own logger.
> --------------------------------------------------------------------------------------------------
>
> Key: TIKA-571
> URL: https://issues.apache.org/jira/browse/TIKA-571
> Project: Tika
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Steve Kearns
>
> In Maven, tika-parsers has a dependency on edu.ucar:netcdf:jar:4.2:compile.
> Inside this netcdf jar is a logging adapter (included in the jar, not as a
> Maven dependency) .
> This prevents well behaved logging behavior for folks using Tika, because
> this logging adapter sits on the classpath, waiting to steal your log
> messages and ignore your preferred logger.
> Here is the offending class that is in the netcdf jar:
> // Compiled from JDK14LoggerAdapter.java (version 1.4 : 48.0, super bit)
> public final class org.slf4j.impl.JDK14LoggerAdapter extends
> org.slf4j.helpers.MarkerIgnoringBase implements
> org.slf4j.spi.LocationAwareLogger {
> It seems that Tika should either re-package the netcdf jar file, or convince
> the netcdf people to make a new release where this isn't a problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
