[GitHub] [tika] THausherr merged pull request #1371: Bump poi.version from 5.2.3 to 5.2.4
THausherr merged PR #1371: URL: https://github.com/apache/tika/pull/1371 -- 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] THausherr merged pull request #1373: Bump io.netty:netty-bom from 4.1.98.Final to 4.1.99.Final
THausherr merged PR #1373: URL: https://github.com/apache/tika/pull/1373 -- 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] THausherr merged pull request #1372: Bump aws.version from 1.12.559 to 1.12.560
THausherr merged PR #1372: URL: https://github.com/apache/tika/pull/1372 -- 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] dependabot[bot] opened a new pull request, #1373: Bump io.netty:netty-bom from 4.1.98.Final to 4.1.99.Final
dependabot[bot] opened a new pull request, #1373: URL: https://github.com/apache/tika/pull/1373 Bumps [io.netty:netty-bom](https://github.com/netty/netty) from 4.1.98.Final to 4.1.99.Final. Commits https://github.com/netty/netty/commit/8e3fe284251d61543cfc37c6b061b63ce6946aaf;>8e3fe28 [maven-release-plugin] prepare release netty-4.1.99.Final https://github.com/netty/netty/commit/97276486599de0d72d16ceeac8802afa2c2249ef;>9727648 Use '-Xcheck:jni' during testsuite run to detect JNI bugs (https://redirect.github.com/netty/netty/issues/13642;>#13642) https://github.com/netty/netty/commit/3fc6566f559207600249bf128d80474b3d06eb04;>3fc6566 Enable build with JDK21 (https://redirect.github.com/netty/netty/issues/13627;>#13627) https://github.com/netty/netty/commit/2fcda074b9adf68ed25a550d8d9dd37d270b4f8f;>2fcda07 Do not try to delete a global handle with the local handles APIs (https://redirect.github.com/netty/netty/issues/13640;>#13640) https://github.com/netty/netty/commit/039493085c4b95535f4e480d7579c7c943ce85c6;>0394930 DefaultDnsCache: apply MAX_SUPPORTED_TTL_SECS cap for negativeTtl (https://redirect.github.com/netty/netty/issues/13637;>#13637) https://github.com/netty/netty/commit/7685b7d50306495f53676e41a421921a47ff8388;>7685b7d Add javadoc for ProxyHandler and its implementations (https://redirect.github.com/netty/netty/issues/13638;>#13638) https://github.com/netty/netty/commit/142027220ab762429c750c3089cfa31d7372dcd2;>1420272 Optimize method HttpStatusClass.valueOf(int) (https://redirect.github.com/netty/netty/issues/13543;>#13543) https://github.com/netty/netty/commit/a258755f393f40903f6711805682097ff703ef55;>a258755 Upgrade maven-settings-action to latest version (https://redirect.github.com/netty/netty/issues/13629;>#13629) https://github.com/netty/netty/commit/4835afdf36e5076029a64f2fccfb98fac3b8769a;>4835afd [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/netty/netty/compare/netty-4.1.98.Final...netty-4.1.99.Final;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] dependabot[bot] opened a new pull request, #1372: Bump aws.version from 1.12.559 to 1.12.560
dependabot[bot] opened a new pull request, #1372: URL: https://github.com/apache/tika/pull/1372 Bumps `aws.version` from 1.12.559 to 1.12.560. Updates `com.amazonaws:aws-java-sdk-s3` from 1.12.559 to 1.12.560 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-s3's changelog. 1.12.560 2023-09-28 AWS Budgets Features Update DescribeBudgets and DescribeBudgetNotificationsForAccount MaxResults limit to 1000. AWS IoT FleetWise Features AWS IoT FleetWise now supports encryption through a customer managed AWS KMS key. The PutEncryptionConfiguration and GetEncryptionConfiguration APIs were added. AWS WAFV2 Features Correct and improve the documentation for the FieldToMatch option JA3 fingerprint. Amazon Bedrock Features Model Invocation logging added to enable or disable logs in customer account. Model listing and description support added. Provisioned Throughput feature added. Custom model support added for creating custom models. Also includes list, and delete functions for custom model. Amazon Bedrock Runtime Features Run Inference: Added support to run the inference on models. Includes set of APIs for running inference in streaming and non-streaming mode. Amazon Elastic Compute Cloud Features Adds support for Customer Managed Key encryption for Amazon Verified Access resources Amazon SageMaker Feature Store Runtime Features Feature Store supports read/write of records with collection type features. Amazon SageMaker Service Features Online store feature groups supports Standard and InMemory tier storage types for low latency storage for real-time data retrieval. The InMemory tier supports collection types List, Set, and Vector. Commits https://github.com/aws/aws-sdk-java/commit/36ae80c6f95c7722cf65c4a799085237beb56deb;>36ae80c AWS SDK for Java 1.12.560 https://github.com/aws/aws-sdk-java/commit/36a799e54ab230a3ed025cd3c7df93156db833ab;>36a799e Update GitHub version number to 1.12.560-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.559...1.12.560;>compare view Updates `com.amazonaws:aws-java-sdk-transcribe` from 1.12.559 to 1.12.560 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-transcribe's changelog. 1.12.560 2023-09-28 AWS Budgets Features Update DescribeBudgets and DescribeBudgetNotificationsForAccount MaxResults limit to 1000. AWS IoT FleetWise Features AWS IoT FleetWise now supports encryption through a customer managed AWS KMS key. The PutEncryptionConfiguration and GetEncryptionConfiguration APIs were added. AWS WAFV2 Features Correct and improve the documentation for the FieldToMatch option JA3 fingerprint. Amazon Bedrock Features Model Invocation logging added to enable or disable logs in customer account. Model listing and description support added. Provisioned Throughput feature added. Custom model support added for creating custom models. Also includes list, and delete functions for custom model. Amazon Bedrock Runtime Features Run Inference: Added support to run the inference on models. Includes set of APIs for running inference in streaming and non-streaming mode. Amazon Elastic Compute Cloud Features Adds support for Customer Managed Key encryption for Amazon Verified Access resources Amazon SageMaker Feature Store Runtime Features Feature Store supports read/write of records with collection type features. Amazon SageMaker Service Features Online store feature groups supports Standard and InMemory tier storage types for low latency storage for real-time data retrieval. The InMemory tier supports collection types List, Set, and Vector. Commits https://github.com/aws/aws-sdk-java/commit/36ae80c6f95c7722cf65c4a799085237beb56deb;>36ae80c AWS SDK for Java 1.12.560 https://github.com/aws/aws-sdk-java/commit/36a799e54ab230a3ed025cd3c7df93156db833ab;>36a799e Update GitHub version number to 1.12.560-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.559...1.12.560;>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---
[GitHub] [tika] dependabot[bot] opened a new pull request, #1371: Bump poi.version from 5.2.3 to 5.2.4
dependabot[bot] opened a new pull request, #1371: URL: https://github.com/apache/tika/pull/1371 Bumps `poi.version` from 5.2.3 to 5.2.4. Updates `org.apache.poi:poi` from 5.2.3 to 5.2.4 Updates `org.apache.poi:poi-ooxml` from 5.2.3 to 5.2.4 Updates `org.apache.poi:poi-scratchpad` from 5.2.3 to 5.2.4 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-4139) Tika modules are not JPMS friendly
[
https://issues.apache.org/jira/browse/TIKA-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770286#comment-17770286
]
Maxim Solodovnik commented on TIKA-4139:
Done TIKA-4147 :)
> Tika modules are not JPMS friendly
> --
>
> Key: TIKA-4139
> URL: https://issues.apache.org/jira/browse/TIKA-4139
> Project: Tika
> Issue Type: Improvement
>Affects Versions: 2.9.0
>Reporter: Maxim Solodovnik
>Priority: Major
> Fix For: 3.0.0-BETA
>
>
> Hello,
> Tika-3 has some major changes, let's add some more :)
> Recently I got following warning while trying to use Tika in JPMS web
> application:
> {code}
> [INFO] --- compiler:3.11.0:compile (default-compile) @ openmeetings-util ---
> [WARNING] Can't extract module name from
> tika-parsers-standard-package-2.9.0.jar: tika.parsers.standard.package:
> Invalid module name: 'package' is not a Java identifier
> {code}
> I've checked {code}main{code} branch and find no {{module-info.java}} and
> {{Automatic-Module-Name}} also doesn't set.
> Maybe {{Automatic-Module-Name}} can be added to Tika modules?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (TIKA-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
[ https://issues.apache.org/jira/browse/TIKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770177#comment-17770177 ] Tim Allison commented on TIKA-4145: --- Merged for now. We can revert the revert if anyone has any concerns. > Consider reverting CloseShieldInputStream.wrap() for back compat > > > Key: TIKA-4145 > URL: https://issues.apache.org/jira/browse/TIKA-4145 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Over on Nutch, we found that hadoop in distributed mode enforces its > dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a > version of commons-io that does not include CloseShieldInputStream.wrap(). > This issue should be fixed in hadoop 3.4.x, but we have no idea how far off > that release is. > From commons-io's documentation, there's no performance benefit from > wrap()... it only helps when debugging in an IDE. > See: NUTCH-3006 and its links > Maybe do this in the 2.x branch and run a release of 2.9.1 with updated > dependencies soon? > WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
[ https://issues.apache.org/jira/browse/TIKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4145. --- Fix Version/s: 2.9.1 Resolution: Fixed > Consider reverting CloseShieldInputStream.wrap() for back compat > > > Key: TIKA-4145 > URL: https://issues.apache.org/jira/browse/TIKA-4145 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.9.1 > > > Over on Nutch, we found that hadoop in distributed mode enforces its > dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a > version of commons-io that does not include CloseShieldInputStream.wrap(). > This issue should be fixed in hadoop 3.4.x, but we have no idea how far off > that release is. > From commons-io's documentation, there's no performance benefit from > wrap()... it only helps when debugging in an IDE. > See: NUTCH-3006 and its links > Maybe do this in the 2.x branch and run a release of 2.9.1 with updated > dependencies soon? > WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
[ https://issues.apache.org/jira/browse/TIKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770174#comment-17770174 ] ASF GitHub Bot commented on TIKA-4145: -- tballison merged PR #1370: URL: https://github.com/apache/tika/pull/1370 > Consider reverting CloseShieldInputStream.wrap() for back compat > > > Key: TIKA-4145 > URL: https://issues.apache.org/jira/browse/TIKA-4145 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Over on Nutch, we found that hadoop in distributed mode enforces its > dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a > version of commons-io that does not include CloseShieldInputStream.wrap(). > This issue should be fixed in hadoop 3.4.x, but we have no idea how far off > that release is. > From commons-io's documentation, there's no performance benefit from > wrap()... it only helps when debugging in an IDE. > See: NUTCH-3006 and its links > Maybe do this in the 2.x branch and run a release of 2.9.1 with updated > dependencies soon? > WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison merged pull request #1370: TIKA-4145 -- revert CloseShieldInputStream.wrap
tballison merged PR #1370: URL: https://github.com/apache/tika/pull/1370 -- 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-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
[ https://issues.apache.org/jira/browse/TIKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770173#comment-17770173 ] ASF GitHub Bot commented on TIKA-4145: -- tballison opened a new pull request, #1370: URL: https://github.com/apache/tika/pull/1370 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Consider reverting CloseShieldInputStream.wrap() for back compat > > > Key: TIKA-4145 > URL: https://issues.apache.org/jira/browse/TIKA-4145 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Over on Nutch, we found that hadoop in distributed mode enforces its > dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a > version of commons-io that does not include CloseShieldInputStream.wrap(). > This issue should be fixed in hadoop 3.4.x, but we have no idea how far off > that release is. > From commons-io's documentation, there's no performance benefit from > wrap()... it only helps when debugging in an IDE. > See: NUTCH-3006 and its links > Maybe do this in the 2.x branch and run a release of 2.9.1 with updated > dependencies soon? > WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1370: TIKA-4145 -- revert CloseShieldInputStream.wrap
tballison opened a new pull request, #1370: URL: https://github.com/apache/tika/pull/1370 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! -- 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-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
[ https://issues.apache.org/jira/browse/TIKA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770171#comment-17770171 ] ASF GitHub Bot commented on TIKA-4145: -- tballison opened a new pull request, #1369: URL: https://github.com/apache/tika/pull/1369 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Consider reverting CloseShieldInputStream.wrap() for back compat > > > Key: TIKA-4145 > URL: https://issues.apache.org/jira/browse/TIKA-4145 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Over on Nutch, we found that hadoop in distributed mode enforces its > dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a > version of commons-io that does not include CloseShieldInputStream.wrap(). > This issue should be fixed in hadoop 3.4.x, but we have no idea how far off > that release is. > From commons-io's documentation, there's no performance benefit from > wrap()... it only helps when debugging in an IDE. > See: NUTCH-3006 and its links > Maybe do this in the 2.x branch and run a release of 2.9.1 with updated > dependencies soon? > WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison closed pull request #1369: TIKA-4145 -- revert CloseShieldInputStream.wrap
tballison closed pull request #1369: TIKA-4145 -- revert CloseShieldInputStream.wrap URL: https://github.com/apache/tika/pull/1369 -- 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] tballison opened a new pull request, #1369: TIKA-4145 -- revert CloseShieldInputStream.wrap
tballison opened a new pull request, #1369: URL: https://github.com/apache/tika/pull/1369 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! -- 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] [Resolved] (TIKA-4146) Update dependencies in 2.x
[ https://issues.apache.org/jira/browse/TIKA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4146. --- Resolution: Duplicate > Update dependencies in 2.x > -- > > Key: TIKA-4146 > URL: https://issues.apache.org/jira/browse/TIKA-4146 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Dependabot (and more importantly [~tilman]!) are keeping us up-to-date on our > 3.x/main branch. This ticket is for updating dependencies in our 2.x branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4146) Update dependencies in 2.x
[ https://issues.apache.org/jira/browse/TIKA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770099#comment-17770099 ] ASF GitHub Bot commented on TIKA-4146: -- tballison opened a new pull request, #1368: URL: https://github.com/apache/tika/pull/1368 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Update dependencies in 2.x > -- > > Key: TIKA-4146 > URL: https://issues.apache.org/jira/browse/TIKA-4146 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > > Dependabot (and more importantly [~tilman]!) are keeping us up-to-date on our > 3.x/main branch. This ticket is for updating dependencies in our 2.x branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1368: TIKA-4146 -- upgrade dependencies in 2.x
tballison opened a new pull request, #1368: URL: https://github.com/apache/tika/pull/1368 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! -- 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] [Created] (TIKA-4146) Update dependencies in 2.x
Tim Allison created TIKA-4146: - Summary: Update dependencies in 2.x Key: TIKA-4146 URL: https://issues.apache.org/jira/browse/TIKA-4146 Project: Tika Issue Type: Task Reporter: Tim Allison Dependabot (and more importantly [~tilman]!) are keeping us up-to-date on our 3.x/main branch. This ticket is for updating dependencies in our 2.x branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-4145) Consider reverting CloseShieldInputStream.wrap() for back compat
Tim Allison created TIKA-4145: - Summary: Consider reverting CloseShieldInputStream.wrap() for back compat Key: TIKA-4145 URL: https://issues.apache.org/jira/browse/TIKA-4145 Project: Tika Issue Type: Task Reporter: Tim Allison Over on Nutch, we found that hadoop in distributed mode enforces its dependencies getting loaded first. Unfortunately, hadoop 3.3.x is using a version of commons-io that does not include CloseShieldInputStream.wrap(). This issue should be fixed in hadoop 3.4.x, but we have no idea how far off that release is. >From commons-io's documentation, there's no performance benefit from wrap()... >it only helps when debugging in an IDE. See: NUTCH-3006 and its links Maybe do this in the 2.x branch and run a release of 2.9.1 with updated dependencies soon? WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4139) Tika modules are not JPMS friendly
[
https://issues.apache.org/jira/browse/TIKA-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769974#comment-17769974
]
Tim Allison commented on TIKA-4139:
---
>Shall I create new JIRA?
Yes, please!
>Maybe I can write some bash script
Ha, I can do that too. LOL
Relatedly, if you can find any other split packages that we should fix in 3.x,
please let us know.
> Tika modules are not JPMS friendly
> --
>
> Key: TIKA-4139
> URL: https://issues.apache.org/jira/browse/TIKA-4139
> Project: Tika
> Issue Type: Improvement
>Affects Versions: 2.9.0
>Reporter: Maxim Solodovnik
>Priority: Major
> Fix For: 3.0.0-BETA
>
>
> Hello,
> Tika-3 has some major changes, let's add some more :)
> Recently I got following warning while trying to use Tika in JPMS web
> application:
> {code}
> [INFO] --- compiler:3.11.0:compile (default-compile) @ openmeetings-util ---
> [WARNING] Can't extract module name from
> tika-parsers-standard-package-2.9.0.jar: tika.parsers.standard.package:
> Invalid module name: 'package' is not a Java identifier
> {code}
> I've checked {code}main{code} branch and find no {{module-info.java}} and
> {{Automatic-Module-Name}} also doesn't set.
> Maybe {{Automatic-Module-Name}} can be added to Tika modules?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
