[
https://issues.apache.org/jira/browse/TIKA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071935#comment-18071935
]
ASF GitHub Bot commented on TIKA-4699:
--------------------------------------
kwin commented on PR #2752:
URL: https://github.com/apache/tika/pull/2752#issuecomment-4205797475
Still unsure what `tika-parsers-standard-package` is supposed to embed on
its own. Who is supposed to use it and for what purpose? I think having an OSGi
bundle without the third party dependencies would still be beneficial. Then one
can decide between deploying:
1) `tika-bundle-standard` (standard-parsers + their third party dependencies)
2) `tika-standards-parsers-package` (all standard parsers)
The suffix `package` seems a bit fuzzy to me. Is this only supposed to be
used to ease dependency management at compile time (then this should have `pom`
packaging only) or is this supposed to be usable OSGi bundle/JAR to be used in
OSGi containers or the Java Classpath?
> Non optional import-package in org.apache.tika.bundle-standard:
> "com.github.javaparser.resolution"
> --------------------------------------------------------------------------------------------------
>
> Key: TIKA-4699
> URL: https://issues.apache.org/jira/browse/TIKA-4699
> Project: Tika
> Issue Type: Bug
> Components: build
> Affects Versions: 3.3.0
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently lots of imports are marked optional in
> https://github.com/apache/tika/blob/a7e6ac73862d0d8d719ace8b9d0cb6d39efb926b/tika-bundles/tika-bundle-standard/pom.xml#L212-L337.
> Notably missing is {{com.github.javaparser.resolution}}.
> That prevents from using this bundle where this dependency is not provided
> through another bundle:
> {code}
> Unable to resolve org.apache.tika.bundle-standard [15](R 15.0): missing
> requirement [org.apache.tika.bundle-standard [15](R 15.0)]
> osgi.wiring.package; (osgi.wiring.package=com.github.javaparser.resolution)
> Unresolved requirements: [[org.apache.tika.bundle-standard [15](R 15.0)]
> osgi.wiring.package; (osgi.wiring.package=com.github.javaparser.resolution)]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4398)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2308)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1566)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> It is unclear if really some packages of
> https://github.com/javaparser/javaparser are optional and others are
> mandatory or this is just bug in the generated manifest.
> If it is the latter instead of listing each package individually using a
> wildcard is supported to match the package and all its sub packages
> (https://bnd.bndtools.org/heads/import_package.html) is best practice in
> https://github.com/apache/tika/blob/a7e6ac73862d0d8d719ace8b9d0cb6d39efb926b/tika-bundles/tika-bundle-standard/pom.xml#L203
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
