[
https://issues.apache.org/jira/browse/TIKA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934863#action_12934863
]
Chris A. Mattmann commented on TIKA-556:
----------------------------------------
Hey Jukka,
Yep, we noticed this at the very near-end of the last Tika release. The
netcdf-all jar is what I ended up publishing, rather than the minimal netcdf
jar. I had an action to try and fix this on Central. I think that the best way
is to file an issue with Sonatype for MVNCENTRAL, ask them to remove the
existing netcdf 0.8 jar, and then republish the minimal version. This ought to
fix it I think!
Cheers,
Chris
> Problems with the NetCDF jar
> ----------------------------
>
> Key: TIKA-556
> URL: https://issues.apache.org/jira/browse/TIKA-556
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.8
> Reporter: Jukka Zitting
> Priority: Critical
> Fix For: 0.9
>
>
> The NetCDF dependency introduced in 0.8 is causing some trouble in downstream
> projects. Instead of containing just NetCDF classes, the jar includes also
> stuff from various other sources, including slf4j, jdom and various Apache
> Commons libraries. This can easily mess up the classpath of a downstream
> project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
