[
https://issues.apache.org/jira/browse/TIKA-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828486#comment-17828486
]
ASF GitHub Bot commented on TIKA-4038:
--------------------------------------
sandeshkr419 commented on PR #1130:
URL: https://github.com/apache/tika/pull/1130#issuecomment-2007895625
Hi @tballison & @gastaldi,
I was trying to upgrade `tika-parsers-standard-package` 2.6 -> 2.8/2.9 as
after updating `commons-compress` to 1.25.0, I was facing issues with parsing
`IWorkPackageParser` related files (.pages, .key).
Here are more details:
https://github.com/opensearch-project/OpenSearch/pull/12627
When I was bumping up tika dependencies to 2.8.0 or 2.9.0 or 2.9.1, I was
not able to utilize the various parsers which were part of
`tika-parsers-standard-package` jar such as `HtmlParser`, etc listed
[here](https://github.com/opensearch-project/OpenSearch/blob/main/plugins/ingest-attachment/src/main/java/org/opensearch/ingest/attachment/TikaImpl.java#L92).
After the changes in package structure in `tika-parsers-standard-package`
since 2.7.0, is there a change in how the dependencies are consumed now? Any
documented way which I can refer to on how to consume the various parser
implementations which are now not available in the
`tika-parsers-standard-package` now.
> Fix dependency problem in tika-parsers-standard-package
> -------------------------------------------------------
>
> Key: TIKA-4038
> URL: https://issues.apache.org/jira/browse/TIKA-4038
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Blocker
> Fix For: 2.8.0
>
>
> https://github.com/apache/tika/pull/936
> because we weren't packaging the dependencies in the jar, when we set
> createDependencyReducedPom to true, this means that other projects using this
> dependency no longer pull the transitive dependencies.
> Thanks to [~jnioche] for finding this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
