Re: [DISCUSS] Support Elasticsearch in the tika-pipes module?
Hi Tim, I would prefer to cut our suppot for non Apache realm lisences. Thanks, Oleg On Tue, Jul 27, 2021, 00:08 Tim Allison wrote: > All, > > As you may have heard, Amazon forked the last Apache licensed > version of Elasticsearch and is now releasing it as pure ASL 2.0 under > the name "OpenSearch". Elasticsearch's license is no longer open > source.[1] > > Currently the OpenSearch emitter works with the 7.x version of > Elasticsearch. Going forward, when the projects diverge: > > a) do we want to support Elasticsearch and > b) are we able to pull in a non-ASL 2.0 docker image for our unit > tests of Elasticsearch > > Cheers, > >Tim > > > [1] https://www.elastic.co/pricing/faq/licensing >
[jira] [Commented] (TIKA-3495) parent-child in solr emitter doesn't seem to include parent id (_nest_parent_)
[ https://issues.apache.org/jira/browse/TIKA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387645#comment-17387645 ] Hudson commented on TIKA-3495: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #291 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/291/]) TIKA-3495 -- and update opensearch child key to be the same as the one in Solr. Add an ignored es test. (tallison: [https://github.com/apache/tika/commit/e549e445ce4985246b3b2d677c48a22d5b3372cd]) * (edit) tika-pipes/tika-emitters/tika-emitter-opensearch/src/main/java/org/apache/tika/pipes/emitter/opensearch/OpenSearchClient.java * (add) tika-integration-tests/tika-pipes-opensearch-integration-tests/src/test/java/org/apache/tika/pipes/es/tests/TikaPipesES7Test.java * (edit) tika-integration-tests/tika-pipes-opensearch-integration-tests/src/test/java/org/apache/tika/pipes/opensearch/tests/TikaPipesOpenSearchTest.java * (edit) tika-integration-tests/tika-pipes-solr-integration-tests/src/test/java/org/apache/tika/pipes/solr/tests/TikaPipesSolrTestBase.java * (edit) tika-pipes/tika-emitters/tika-emitter-solr/src/test/java/org/apache/tika/pipes/emitter/solr/SolrEmitterDevTest.java > parent-child in solr emitter doesn't seem to include parent id (_nest_parent_) > -- > > Key: TIKA-3495 > URL: https://issues.apache.org/jira/browse/TIKA-3495 > Project: Tika > Issue Type: Bug > Components: tika-pipes >Affects Versions: 2.0.0 >Reporter: Tim Allison >Priority: Minor > Attachments: Screenshot from 2021-07-23 11-21-38.png, Screenshot from > 2021-07-23 11-22-02.png, Screenshot from 2021-07-23 11-45-33.png > > > I'm trying to draft examples of indexing parent-child relationships with the > Solr emitter on the tika-pipes wiki page. With the latest 2.0.1-SNAPSHOT > build, I'm not seeing any of the following fields populated: _root_, > _nest_parent_, _nest_path_. > Should these be auto-populated by Solrj or do we need to add these paths? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS] Support Elasticsearch in the tika-pipes module?
All, As you may have heard, Amazon forked the last Apache licensed version of Elasticsearch and is now releasing it as pure ASL 2.0 under the name "OpenSearch". Elasticsearch's license is no longer open source.[1] Currently the OpenSearch emitter works with the 7.x version of Elasticsearch. Going forward, when the projects diverge: a) do we want to support Elasticsearch and b) are we able to pull in a non-ASL 2.0 docker image for our unit tests of Elasticsearch Cheers, Tim [1] https://www.elastic.co/pricing/faq/licensing
2.0.1?
All, We've made some important cleanups and updated some vulnerable dependencies recently. Should we aim for August 2 or so to start the next release process for 2.0.1 (or 2.1.0?)? Thank you! Cheers, Tim
[jira] [Commented] (TIKA-3498) Fix dependency convergence and other import issues in scientific vs standard package
[
https://issues.apache.org/jira/browse/TIKA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387484#comment-17387484
]
Hudson commented on TIKA-3498:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #290 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/290/])
TIKA-3498 -- fix dependency convergence in tika-standard and scientific parsers
modules (tallison:
[https://github.com/apache/tika/commit/f24c15088ca96c140394a536eed31b76ded06b4f])
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pkg-module/pom.xml
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-news-module/pom.xml
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-code-module/pom.xml
* (edit)
tika-parsers/tika-parsers-extended/tika-parser-scientific-module/pom.xml
* (edit) tika-parent/pom.xml
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/pom.xml
> Fix dependency convergence and other import issues in scientific vs standard
> package
>
>
> Key: TIKA-3498
> URL: https://issues.apache.org/jira/browse/TIKA-3498
> Project: Tika
> Issue Type: Bug
>Reporter: Tim Allison
>Assignee: Tim Allison
>Priority: Major
> Fix For: 2.0.1
>
>
> [~dadoonet] found that there's a convergence error when users include both
> the tika-parsers-standard-package jar and tika-parser-scientific-module.
> {noformat}
> Dependency convergence error for org.slf4j:jcl-over-slf4j:1.7.31 paths to
> dependency are:
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parsers-standard-package:2.0.0
> +-org.slf4j:jcl-over-slf4j:1.7.31
> and
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parser-scientific-module:2.0.0
> +-edu.ucar:netcdf4:4.5.5
> +-edu.ucar:cdm:4.5.5
> +-org.slf4j:jcl-over-slf4j:1.7.7
> {noformat}
> [~dadoonet] also found that ucar's quartz dependency causes problems with CVE
> checkers. We should update that dependency as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (TIKA-3495) parent-child in solr emitter doesn't seem to include parent id (_nest_parent_)
[ https://issues.apache.org/jira/browse/TIKA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387483#comment-17387483 ] Hudson commented on TIKA-3495: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #290 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/290/]) TIKA-3495 - verify embedded docs work (#449) (github: [https://github.com/apache/tika/commit/6c30f2b273a7ad5b820cb236df129da71d1590b5]) * (add) tika-integration-tests/tika-pipes-solr-integration-tests/src/test/resources/embedded/embedded.docx * (edit) tika-integration-tests/tika-pipes-solr-integration-tests/src/test/java/org/apache/tika/pipes/solr/tests/TikaPipesSolrTestBase.java * (edit) tika-pipes/tika-emitters/tika-emitter-solr/src/main/java/org/apache/tika/pipes/emitter/solr/SolrEmitter.java > parent-child in solr emitter doesn't seem to include parent id (_nest_parent_) > -- > > Key: TIKA-3495 > URL: https://issues.apache.org/jira/browse/TIKA-3495 > Project: Tika > Issue Type: Bug > Components: tika-pipes >Affects Versions: 2.0.0 >Reporter: Tim Allison >Priority: Minor > Attachments: Screenshot from 2021-07-23 11-21-38.png, Screenshot from > 2021-07-23 11-22-02.png, Screenshot from 2021-07-23 11-45-33.png > > > I'm trying to draft examples of indexing parent-child relationships with the > Solr emitter on the tika-pipes wiki page. With the latest 2.0.1-SNAPSHOT > build, I'm not seeing any of the following fields populated: _root_, > _nest_parent_, _nest_path_. > Should these be auto-populated by Solrj or do we need to add these paths? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TIKA-3492) Upgrade version for TPS: rome to 1.16.0 in tika-bundle
[ https://issues.apache.org/jira/browse/TIKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387482#comment-17387482 ] Hudson commented on TIKA-3492: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #290 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/290/]) TIKA-3492 - upgrade rometools (tallison: [https://github.com/apache/tika/commit/d62decc7dd36cbe85fccc6b9bac63d13d7b4324d]) * (edit) tika-parent/pom.xml > Upgrade version for TPS: rome to 1.16.0 in tika-bundle > -- > > Key: TIKA-3492 > URL: https://issues.apache.org/jira/browse/TIKA-3492 > Project: Tika > Issue Type: Bug >Affects Versions: 1.27 >Reporter: Shubhangi Raut >Priority: Major > Labels: upgrade > Fix For: 2.0.1, 1.28 > > > tika-bundle-1.27 uses rome-1.15.0. > There is following vulnerability reported in rome-1.15.0 as per Sonatype Data > Research: > [sonatype-2021-0802|https://vw-pun-bpm-bl15.bmc.com:8070/ui/links/vln/sonatype-2021-0802] > : > [rome-1.16.0|https://mvnrepository.com/artifact/com.rometools/rome/1.16.0] is > non-vulnerable version. Please consider upgrading to it in the next release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TIKA-3492) Upgrade version for TPS: rome to 1.16.0 in tika-bundle
[ https://issues.apache.org/jira/browse/TIKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387465#comment-17387465 ] Hudson commented on TIKA-3492: -- SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #142 (See [https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/142/]) TIKA-3492 -- upgrade rometools (tallison: [https://github.com/apache/tika/commit/8dc6c5c0e4200838a97000788da4852dea73a614]) * (edit) tika-parsers/pom.xml > Upgrade version for TPS: rome to 1.16.0 in tika-bundle > -- > > Key: TIKA-3492 > URL: https://issues.apache.org/jira/browse/TIKA-3492 > Project: Tika > Issue Type: Bug >Affects Versions: 1.27 >Reporter: Shubhangi Raut >Priority: Major > Labels: upgrade > Fix For: 2.0.1, 1.28 > > > tika-bundle-1.27 uses rome-1.15.0. > There is following vulnerability reported in rome-1.15.0 as per Sonatype Data > Research: > [sonatype-2021-0802|https://vw-pun-bpm-bl15.bmc.com:8070/ui/links/vln/sonatype-2021-0802] > : > [rome-1.16.0|https://mvnrepository.com/artifact/com.rometools/rome/1.16.0] is > non-vulnerable version. Please consider upgrading to it in the next release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TIKA-3478) Extract "desc" metadata field from AppleUserBox in MP4
[ https://issues.apache.org/jira/browse/TIKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387466#comment-17387466 ] Hudson commented on TIKA-3478: -- SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #142 (See [https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/142/]) TIKA-3478 -- extract desc field from mp4s (tallison: [https://github.com/apache/tika/commit/741556dc6ac8b51fc99e20d45a3a310a78e6b5c9]) * (edit) tika-parsers/src/main/java/org/apache/tika/parser/mp4/boxes/TikaUserDataBox.java > Extract "desc" metadata field from AppleUserBox in MP4 > -- > > Key: TIKA-3478 > URL: https://issues.apache.org/jira/browse/TIKA-3478 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Assignee: Tim Allison >Priority: Trivial > Fix For: 2.0.0, 1.28 > > > In recent regression testing comparing 1.x with 2.x, Mp4s were missing text. > On the few handful of files that I've reviewed, the cause was that we were > pulling "ldes" as the description field, and it turns out there can also be a > "desc" field. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TIKA-3498) Fix dependency convergence and other import issues in scientific vs standard package
[
https://issues.apache.org/jira/browse/TIKA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3498.
---
Fix Version/s: 2.0.1
Assignee: Tim Allison
Resolution: Fixed
Thank you [~dadoonet]! Please let us know whatever else you find!
> Fix dependency convergence and other import issues in scientific vs standard
> package
>
>
> Key: TIKA-3498
> URL: https://issues.apache.org/jira/browse/TIKA-3498
> Project: Tika
> Issue Type: Bug
>Reporter: Tim Allison
>Assignee: Tim Allison
>Priority: Major
> Fix For: 2.0.1
>
>
> [~dadoonet] found that there's a convergence error when users include both
> the tika-parsers-standard-package jar and tika-parser-scientific-module.
> {noformat}
> Dependency convergence error for org.slf4j:jcl-over-slf4j:1.7.31 paths to
> dependency are:
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parsers-standard-package:2.0.0
> +-org.slf4j:jcl-over-slf4j:1.7.31
> and
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parser-scientific-module:2.0.0
> +-edu.ucar:netcdf4:4.5.5
> +-edu.ucar:cdm:4.5.5
> +-org.slf4j:jcl-over-slf4j:1.7.7
> {noformat}
> [~dadoonet] also found that ucar's quartz dependency causes problems with CVE
> checkers. We should update that dependency as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (TIKA-3492) Upgrade version for TPS: rome to 1.16.0 in tika-bundle
[ https://issues.apache.org/jira/browse/TIKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-3492. --- Fix Version/s: 1.28 2.0.1 Resolution: Fixed > Upgrade version for TPS: rome to 1.16.0 in tika-bundle > -- > > Key: TIKA-3492 > URL: https://issues.apache.org/jira/browse/TIKA-3492 > Project: Tika > Issue Type: Bug >Affects Versions: 1.27 >Reporter: Shubhangi Raut >Priority: Major > Labels: upgrade > Fix For: 2.0.1, 1.28 > > > tika-bundle-1.27 uses rome-1.15.0. > There is following vulnerability reported in rome-1.15.0 as per Sonatype Data > Research: > [sonatype-2021-0802|https://vw-pun-bpm-bl15.bmc.com:8070/ui/links/vln/sonatype-2021-0802] > : > [rome-1.16.0|https://mvnrepository.com/artifact/com.rometools/rome/1.16.0] is > non-vulnerable version. Please consider upgrading to it in the next release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TIKA-3478) Extract "desc" metadata field from AppleUserBox in MP4
[ https://issues.apache.org/jira/browse/TIKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-3478: -- Fix Version/s: 1.28 > Extract "desc" metadata field from AppleUserBox in MP4 > -- > > Key: TIKA-3478 > URL: https://issues.apache.org/jira/browse/TIKA-3478 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Assignee: Tim Allison >Priority: Trivial > Fix For: 2.0.0, 1.28 > > > In recent regression testing comparing 1.x with 2.x, Mp4s were missing text. > On the few handful of files that I've reviewed, the cause was that we were > pulling "ldes" as the description field, and it turns out there can also be a > "desc" field. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TIKA-3495) parent-child in solr emitter doesn't seem to include parent id (_nest_parent_)
[ https://issues.apache.org/jira/browse/TIKA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387423#comment-17387423 ] ASF GitHub Bot commented on TIKA-3495: -- tballison merged pull request #449: URL: https://github.com/apache/tika/pull/449 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > parent-child in solr emitter doesn't seem to include parent id (_nest_parent_) > -- > > Key: TIKA-3495 > URL: https://issues.apache.org/jira/browse/TIKA-3495 > Project: Tika > Issue Type: Bug > Components: tika-pipes >Affects Versions: 2.0.0 >Reporter: Tim Allison >Priority: Minor > Attachments: Screenshot from 2021-07-23 11-21-38.png, Screenshot from > 2021-07-23 11-22-02.png, Screenshot from 2021-07-23 11-45-33.png > > > I'm trying to draft examples of indexing parent-child relationships with the > Solr emitter on the tika-pipes wiki page. With the latest 2.0.1-SNAPSHOT > build, I'm not seeing any of the following fields populated: _root_, > _nest_parent_, _nest_path_. > Should these be auto-populated by Solrj or do we need to add these paths? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [tika] tballison merged pull request #449: TIKA-3495 - verify embedded docs work
tballison merged pull request #449: URL: https://github.com/apache/tika/pull/449 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-3497) Update README for installing Tika Server as a service for 2.0 release
[ https://issues.apache.org/jira/browse/TIKA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387418#comment-17387418 ] ASF GitHub Bot commented on TIKA-3497: -- tballison merged pull request #448: URL: https://github.com/apache/tika/pull/448 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update README for installing Tika Server as a service for 2.0 release > - > > Key: TIKA-3497 > URL: https://issues.apache.org/jira/browse/TIKA-3497 > Project: Tika > Issue Type: Improvement > Components: server >Affects Versions: 2.0.0-ALPHA >Reporter: David Eric Pugh >Priority: Minor > Fix For: 2.0.1 > > > Some small tweaks after manually testing the scripts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [tika] tballison merged pull request #448: TIKA-3497 bump versions in example commands for installing as a service.
tballison merged pull request #448: URL: https://github.com/apache/tika/pull/448 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-3498) Fix dependency convergence and other import issues in scientific vs standard package
[
https://issues.apache.org/jira/browse/TIKA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387416#comment-17387416
]
Tim Allison commented on TIKA-3498:
---
Looks like we were bundling log4j2 in the microsoft parsers module. :P Ugh.
Fixing that as well.
> Fix dependency convergence and other import issues in scientific vs standard
> package
>
>
> Key: TIKA-3498
> URL: https://issues.apache.org/jira/browse/TIKA-3498
> Project: Tika
> Issue Type: Bug
>Reporter: Tim Allison
>Priority: Major
>
> [~dadoonet] found that there's a convergence error when users include both
> the tika-parsers-standard-package jar and tika-parser-scientific-module.
> {noformat}
> Dependency convergence error for org.slf4j:jcl-over-slf4j:1.7.31 paths to
> dependency are:
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parsers-standard-package:2.0.0
> +-org.slf4j:jcl-over-slf4j:1.7.31
> and
> +-org.example:tika-import-test:1.0-SNAPSHOT
> +-org.apache.tika:tika-parser-scientific-module:2.0.0
> +-edu.ucar:netcdf4:4.5.5
> +-edu.ucar:cdm:4.5.5
> +-org.slf4j:jcl-over-slf4j:1.7.7
> {noformat}
> [~dadoonet] also found that ucar's quartz dependency causes problems with CVE
> checkers. We should update that dependency as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (TIKA-3498) Fix dependency convergence and other import issues in scientific vs standard package
Tim Allison created TIKA-3498:
-
Summary: Fix dependency convergence and other import issues in
scientific vs standard package
Key: TIKA-3498
URL: https://issues.apache.org/jira/browse/TIKA-3498
Project: Tika
Issue Type: Bug
Reporter: Tim Allison
[~dadoonet] found that there's a convergence error when users include both the
tika-parsers-standard-package jar and tika-parser-scientific-module.
{noformat}
Dependency convergence error for org.slf4j:jcl-over-slf4j:1.7.31 paths to
dependency are:
+-org.example:tika-import-test:1.0-SNAPSHOT
+-org.apache.tika:tika-parsers-standard-package:2.0.0
+-org.slf4j:jcl-over-slf4j:1.7.31
and
+-org.example:tika-import-test:1.0-SNAPSHOT
+-org.apache.tika:tika-parser-scientific-module:2.0.0
+-edu.ucar:netcdf4:4.5.5
+-edu.ucar:cdm:4.5.5
+-org.slf4j:jcl-over-slf4j:1.7.7
{noformat}
[~dadoonet] also found that ucar's quartz dependency causes problems with CVE
checkers. We should update that dependency as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [tika] dadoonet commented on pull request #269: Update soap-api to 1.4.0 and stax-ex to 1.8.1
dadoonet commented on pull request #269: URL: https://github.com/apache/tika/pull/269#issuecomment-886750703 I believe that we can close this one? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [tika] dadoonet closed pull request #269: Update soap-api to 1.4.0 and stax-ex to 1.8.1
dadoonet closed pull request #269: URL: https://github.com/apache/tika/pull/269 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (TIKA-3367) Add Bill of Materials (BOM) artifact
[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3367: Fix Version/s: (was: 2.0.0-BETA) 2.0.1 > Add Bill of Materials (BOM) artifact > > > Key: TIKA-3367 > URL: https://issues.apache.org/jira/browse/TIKA-3367 > Project: Tika > Issue Type: Improvement > Components: packaging >Reporter: Konstantin Gribov >Assignee: Konstantin Gribov >Priority: Major > Fix For: 2.0.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
