[GitHub] [tika] dependabot[bot] opened a new pull request, #1340: Bump com.azure:azure-storage-blob from 12.23.1 to 12.24.0
dependabot[bot] opened a new pull request, #1340: URL: https://github.com/apache/tika/pull/1340 Bumps [com.azure:azure-storage-blob](https://github.com/Azure/azure-sdk-for-java) from 12.23.1 to 12.24.0. Release notes Sourced from https://github.com/Azure/azure-sdk-for-java/releases;>com.azure:azure-storage-blob's releases. azure-storage-blob_12.24.0 12.24.0 (2023-09-12) Features Added Added support for service versions 2023-05-03 and 2023-08-03. Added RehydratePendingToCold value to ArchiveStatus enum. Commits https://github.com/Azure/azure-sdk-for-java/commit/f87dd12afbcb4214a7464ec0fdaf819b3c21a28c;>f87dd12 STG90 GA Release 2023-09-12 (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36728;>#36728) https://github.com/Azure/azure-sdk-for-java/commit/63b3ac7a503949eb7f382657814aa55ed72053b1;>63b3ac7 Adding deleteRecursivelyWithResponse for DataLakeDirectoryClient (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36726;>#36726) https://github.com/Azure/azure-sdk-for-java/commit/f4c38bb15bf2aeeb2d584dc6fc706113514ad2fd;>f4c38bb Close OkHttp ResponseBody after writeBodyTo and writeBodyToAsync (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36650;>#36650) https://github.com/Azure/azure-sdk-for-java/commit/d26e243c6f3fcb7c3484a15eb45b9b9f0bf3ac77;>d26e243 Documentation Fixes (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36635;>#36635) https://github.com/Azure/azure-sdk-for-java/commit/8b17067ff98eb0a5bbfb7ada8a664d4aa272ff09;>8b17067 Modify UserAgent header for client-side Encryption (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36614;>#36614) https://github.com/Azure/azure-sdk-for-java/commit/0afdf4450affb482342dff7f5de87e926399a389;>0afdf44 Increment package versions for identity releases (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36701;>#36701) https://github.com/Azure/azure-sdk-for-java/commit/57aa1413beb0457e503e61d627bb5e33525cb8a9;>57aa141 reduceNoisyLogLevelFromInfoToDebug (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36653;>#36653) https://github.com/Azure/azure-sdk-for-java/commit/eaa16d1dc3217ef3abd66a2d1740966491572e79;>eaa16d1 Organize the Spring directory (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36692;>#36692) https://github.com/Azure/azure-sdk-for-java/commit/360301f7dca76bc46213ea7d0b5e2fb68ec1ee89;>360301f mgmt, update containerregistry to 2023-07-01 (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36688;>#36688) https://github.com/Azure/azure-sdk-for-java/commit/9aea12688e53d9edde8329d0429544884070012b;>9aea126 Adding support for case insensitive metadata keys on encrypted blobs (https://redirect.github.com/Azure/azure-sdk-for-java/issues/36567;>#36567) Additional commits viewable in https://github.com/Azure/azure-sdk-for-java/compare/azure-storage-blob_12.23.1...azure-storage-blob_12.24.0;>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
[GitHub] [tika] dependabot[bot] opened a new pull request, #1339: Bump com.google.cloud:google-cloud-storage from 2.26.1 to 2.27.0
dependabot[bot] opened a new pull request, #1339: URL: https://github.com/apache/tika/pull/1339 Bumps [com.google.cloud:google-cloud-storage](https://github.com/googleapis/java-storage) from 2.26.1 to 2.27.0. Release notes Sourced from https://github.com/googleapis/java-storage/releases;>com.google.cloud:google-cloud-storage's releases. v2.27.0 https://github.com/googleapis/java-storage/compare/v2.26.1...v2.27.0;>2.27.0 (2023-09-12) Features Add new JournalingBlobWriteSessionConfig usable with gRPC transport (https://redirect.github.com/googleapis/java-storage/issues/2194;>#2194) (https://github.com/googleapis/java-storage/commit/8880d94c3d1a737dd4492cf66a16ba5e08633a70;>8880d94) Follow-up CLI Improvements (https://redirect.github.com/googleapis/java-storage/issues/2184;>#2184) (https://github.com/googleapis/java-storage/commit/d9859768081ea6f872097851d3e318b5bad384d9;>d985976) Initial CLI for SSB integration and Workload 1 (https://redirect.github.com/googleapis/java-storage/issues/2166;>#2166) (https://github.com/googleapis/java-storage/commit/a349735e7fe108e623a330afec0c8cd608ebeef9;>a349735) Bug Fixes A resumable session without a Range header should be interpreted as 0 length (https://redirect.github.com/googleapis/java-storage/issues/2182;>#2182) (https://github.com/googleapis/java-storage/commit/53022011d83e6a8515a5ba008fc45fc2dae39cea;>5302201) Update User-Agent handling for resumable uploads (https://redirect.github.com/googleapis/java-storage/issues/2168;>#2168) (https://github.com/googleapis/java-storage/commit/665b714f421d3c13b557d0ff71460c328c010856;>665b714) Update version resolution logic to be more resilient (https://redirect.github.com/googleapis/java-storage/issues/2169;>#2169) (https://github.com/googleapis/java-storage/commit/c89d27508039a014ea5a6dd8d4889f63d07db73f;>c89d275) Dependencies Update actions/checkout action to v4 (https://redirect.github.com/googleapis/java-storage/issues/2188;>#2188) (https://github.com/googleapis/java-storage/commit/c10267e176bda21cd5755dfb0e96d0504fbc1d54;>c10267e) Update actions/checkout action to v4 (https://redirect.github.com/googleapis/java-storage/issues/2189;>#2189) (https://github.com/googleapis/java-storage/commit/5c048c499eef224dade8f4409dfae732cb5a7017;>5c048c4) Update actions/checkout action to v4 (https://redirect.github.com/googleapis/java-storage/issues/2190;>#2190) (https://github.com/googleapis/java-storage/commit/45e66e89373ef016eff9b7deb30dbdfa818770d2;>45e66e8) Update dependency com.google.apis:google-api-services-storage to v1-rev20230710-2.0.0 (https://redirect.github.com/googleapis/java-storage/issues/2162;>#2162) (https://github.com/googleapis/java-storage/commit/73a9f75d000d2a59cd680fd383a9f9e1b91570cf;>73a9f75) Update dependency com.google.apis:google-api-services-storage to v1-rev20230907-2.0.0 (https://redirect.github.com/googleapis/java-storage/issues/2200;>#2200) (https://github.com/googleapis/java-storage/commit/1fa49db2810f6ffbd46755b4eb1f5efdcf980edb;>1fa49db) Update dependency com.google.cloud:google-cloud-shared-dependencies to v3.15.0 (https://redirect.github.com/googleapis/java-storage/issues/2197;>#2197) (https://github.com/googleapis/java-storage/commit/26552f4b78f77d90df4e3dfb829c3f9c092fc817;>26552f4) Update dependency info.picocli:picocli to v4.7.4 (https://redirect.github.com/googleapis/java-storage/issues/2177;>#2177) (https://github.com/googleapis/java-storage/commit/0c908147375fe58ac280179f5fba10bdd3886003;>0c90814) Update dependency info.picocli:picocli to v4.7.5 (https://redirect.github.com/googleapis/java-storage/issues/2183;>#2183) (https://github.com/googleapis/java-storage/commit/f2448615ded6d9f43344bf1b9cda7ae3b191223b;>f244861) Update dependency net.jqwik:jqwik to v1.8.0 (https://redirect.github.com/googleapis/java-storage/issues/2187;>#2187) (https://github.com/googleapis/java-storage/commit/aedbd6a811c4fcfedff68d7d46bb68e93bf9;>aedbd6a) Update dependency org.graalvm.buildtools:native-maven-plugin to v0.9.26 (https://redirect.github.com/googleapis/java-storage/issues/2196;>#2196) (https://github.com/googleapis/java-storage/commit/4f8bb658e9ff3cba5e745acae13ec4094a1a48d5;>4f8bb65) Changelog Sourced from https://github.com/googleapis/java-storage/blob/main/CHANGELOG.md;>com.google.cloud:google-cloud-storage's changelog. https://github.com/googleapis/java-storage/compare/v2.26.1...v2.27.0;>2.27.0 (2023-09-12) Features Add new JournalingBlobWriteSessionConfig usable with gRPC transport (https://redirect.github.com/googleapis/java-storage/issues/2194;>#2194) (https://github.com/googleapis/java-storage/commit/8880d94c3d1a737dd4492cf66a16ba5e08633a70;>8880d94) Follow-up CLI Improvements (https://redirect.github.com/googleapis/java-storage/issues/2184;>#2184)
[GitHub] [tika] dependabot[bot] opened a new pull request, #1338: Bump aws.version from 1.12.549 to 1.12.550
dependabot[bot] opened a new pull request, #1338: URL: https://github.com/apache/tika/pull/1338 Bumps `aws.version` from 1.12.549 to 1.12.550. Updates `com.amazonaws:aws-java-sdk-s3` from 1.12.549 to 1.12.550 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-s3's changelog. 1.12.550 2023-09-13 AWS Cloud9 Features Update to include information on Ubuntu 18 deprecation. AWS SimSpace Weaver Features Edited the introductory text for the API reference. AWS X-Ray Features Add StartTime field in GetTraceSummaries API response for each TraceSummary. Amazon CloudWatch Internet Monitor Features This release updates the Amazon CloudWatch Internet Monitor API domain name. Amazon GuardDuty Features Add managementType field to ListCoverage API response. Amazon Interactive Video Service RealTime Features Doc only update that changes description for ParticipantToken. Amazon Kinesis Firehose Features DocumentIdOptions has been added for the Amazon OpenSearch destination. Elastic Disaster Recovery Service Features Updated existing APIs and added new ones to support using AWS Elastic Disaster Recovery post-launch actions. Added support for new regions. Commits https://github.com/aws/aws-sdk-java/commit/0bac15b42bc826c005d112f026955b8746b56985;>0bac15b AWS SDK for Java 1.12.550 https://github.com/aws/aws-sdk-java/commit/e0df76d027be8fe741ffef7538554e94cc218894;>e0df76d Update GitHub version number to 1.12.550-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.549...1.12.550;>compare view Updates `com.amazonaws:aws-java-sdk-transcribe` from 1.12.549 to 1.12.550 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-transcribe's changelog. 1.12.550 2023-09-13 AWS Cloud9 Features Update to include information on Ubuntu 18 deprecation. AWS SimSpace Weaver Features Edited the introductory text for the API reference. AWS X-Ray Features Add StartTime field in GetTraceSummaries API response for each TraceSummary. Amazon CloudWatch Internet Monitor Features This release updates the Amazon CloudWatch Internet Monitor API domain name. Amazon GuardDuty Features Add managementType field to ListCoverage API response. Amazon Interactive Video Service RealTime Features Doc only update that changes description for ParticipantToken. Amazon Kinesis Firehose Features DocumentIdOptions has been added for the Amazon OpenSearch destination. Elastic Disaster Recovery Service Features Updated existing APIs and added new ones to support using AWS Elastic Disaster Recovery post-launch actions. Added support for new regions. Commits https://github.com/aws/aws-sdk-java/commit/0bac15b42bc826c005d112f026955b8746b56985;>0bac15b AWS SDK for Java 1.12.550 https://github.com/aws/aws-sdk-java/commit/e0df76d027be8fe741ffef7538554e94cc218894;>e0df76d Update GitHub version number to 1.12.550-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.549...1.12.550;>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) --- 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) -
[jira] [Commented] (TIKA-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764952#comment-17764952 ] ASF GitHub Bot commented on TIKA-3948: -- solomax opened a new pull request, #1337: URL: https://github.com/apache/tika/pull/1337 @tballison the build is RED and it would be hard to fix this :( The problem is `org.apache.sis*` hardly uses `jaxb-runtime` `2.3.3` (which is NOT compatible with `4.0.3`) I'm afraid we should contact Apache SIS :) > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] solomax opened a new pull request, #1337: [TIKA-3948] start moving to Jakarta
solomax opened a new pull request, #1337: URL: https://github.com/apache/tika/pull/1337 @tballison the build is RED and it would be hard to fix this :( The problem is `org.apache.sis*` hardly uses `jaxb-runtime` `2.3.3` (which is NOT compatible with `4.0.3`) I'm afraid we should contact Apache SIS :) -- 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-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764939#comment-17764939 ] Maxim Solodovnik commented on TIKA-3948: > Spring 6 requires Java 17 so that won't work unless we go big and go straight > to 17... CXF4 depends on Spring6 (optional dependency) https://mvnrepository.com/artifact/org.apache.cxf/cxf-core/4.0.2 I'll try to create PR this week :) [~tallison] What is the best way to test nothing is broken? > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3641) Upgrade to Lucene 9.x
[
https://issues.apache.org/jira/browse/TIKA-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764874#comment-17764874
]
Hudson commented on TIKA-3641:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1244 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1244/])
TIKA-3641 -- upgrade Lucene to 9.x now that we're on Java 11 (#1335) (github:
[https://github.com/apache/tika/commit/0960d74513b1ad705b38ec5c1710b88f30a4e5a1])
* (delete)
tika-eval/tika-eval-core/src/main/resources/META-INF/services/org.apache.lucene.analysis.util.TokenFilterFactory
* (edit) tika-parent/pom.xml
* (edit) tika-eval/tika-eval-app/pom.xml
* (edit)
tika-eval/tika-eval-app/src/main/java/org/apache/tika/eval/app/tools/SlowCompositeReaderWrapper.java
* (edit)
tika-eval/tika-eval-core/src/main/java/org/apache/tika/eval/core/tokens/CJKBigramAwareLengthFilterFactory.java
* (edit) tika-eval/tika-eval-core/pom.xml
* (edit)
tika-eval/tika-eval-core/src/main/java/org/apache/tika/eval/core/tokens/AnalyzerDeserializer.java
* (edit)
tika-eval/tika-eval-core/src/main/java/org/apache/tika/eval/core/tokens/URLEmailNormalizingFilterFactory.java
* (edit)
tika-eval/tika-eval-core/src/main/java/org/apache/tika/eval/core/tokens/AlphaIdeographFilterFactory.java
* (edit) tika-server/tika-server-eval/pom.xml
* (add)
tika-eval/tika-eval-core/src/main/resources/META-INF/services/org.apache.lucene.analysis.TokenFilterFactory
> Upgrade to Lucene 9.x
> -
>
> Key: TIKA-3641
> URL: https://issues.apache.org/jira/browse/TIKA-3641
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Minor
> Fix For: 3.0.0-BETA
>
>
> This is a non-trivial upgrade. I don't think it will buy us much, but we
> should do it in our {{main}} branch at some point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (TIKA-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764875#comment-17764875 ] Hudson commented on TIKA-4129: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1244 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1244/]) TIKA-4129 -- upgrade dependencies that require java 11. (#1336) (github: [https://github.com/apache/tika/commit/2e19dc06e806b933ecec23f83538d9dd43b78cfa]) * (edit) tika-parent/pom.xml > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Fix For: 3.0.0-BETA > > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Hi Tim, I think jumping to Java 17 would be a bit much for 3.x. I would vote for a shorter EOL for Tika 2.x What I’ve seen is that users who are forced to continue using older versions of Java are generally able to back port changes they need, once support is EOL. So if there’s a critical bug fix in 3.x in 9 months, anyone still on Java 8 would be able to fork/fix it themselves, without relying on the (small, over-loaded) Tika community to keep Java 8 actively supported. — Ken > On Sep 13, 2023, at 12:26 PM, Tim Allison wrote: > > We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one > more year. I've started the branches and started making some changes in this > direction. > > Is it worth pushing this modernization further or faster, with either: > a) Jump to Java 17 now and keep Java 8 in 2.x for one more year > b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say > 6 months or fewer? > > Thank you, all, for your feedback! > > Best, > > Tim > > -- Ken Krugler http://www.scaleunlimited.com Custom big data solutions Flink, Pinot, Solr, Elasticsearch
[jira] [Commented] (TIKA-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764860#comment-17764860 ] Tim Allison commented on TIKA-3948: --- Spring 6 requires Java 17 so that won't work unless we go big and go straight to 17... > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764859#comment-17764859 ] Tim Allison commented on TIKA-3948: --- I started a TIKA-3948 branch. I think we need to start using the eclipse transformer plugin for a number of dependencies? https://github.com/eclipse/transformer/blob/main/maven-plugins/transformer-maven-plugin/README.md Help. > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-4128) Bump main to java 11
[ https://issues.apache.org/jira/browse/TIKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4128. --- Fix Version/s: 3.0.0-BETA Resolution: Fixed > Bump main to java 11 > > > Key: TIKA-4128 > URL: https://issues.apache.org/jira/browse/TIKA-4128 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Fix For: 3.0.0-BETA > > > Aside from setting maven compiler plugin's release to 11, there are a > smattering of other fixes/updates we need to make. > There are quite a few checkstyle issues for deprecated API calls, mostly > around newInstance(). > We need to delete our java 8 github workflow. > There are a couple of other things we'll want to update as well on other > tickets (jakarta and dependencies that require > 8). > This ticket just gets us started into Java 11 on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4128) Bump main to java 11
[ https://issues.apache.org/jira/browse/TIKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764849#comment-17764849 ] Hudson commented on TIKA-4128: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1243 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1243/]) TIKA-4128 -- bump to Java 11 (#1334) (github: [https://github.com/apache/tika/commit/966799a1cac08d0dd7e751aabe6b6935e8448a04]) * (edit) tika-parsers/tika-parsers-ml/tika-parser-nlp-module/src/main/java/org/apache/tika/parser/ner/NamedEntityParser.java * (edit) tika-core/src/main/java/org/apache/tika/config/ConfigBase.java * (delete) .github/workflows/main-jdk8-build.yml * (edit) tika-core/src/main/java/org/apache/tika/config/Param.java * (edit) tika-core/src/main/java/org/apache/tika/utils/XMLReaderUtils.java * (edit) tika-parent/pom.xml * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/FndStructureConstants.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/OneNotePtr.java * (edit) tika-core/src/main/java/org/apache/tika/config/TikaConfig.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/fsshttpb/streamobj/StreamObject.java * (edit) tika-xmp/src/main/java/org/apache/tika/xmp/convert/TikaToXMP.java * (edit) .github/workflows/main-jdk11-build.yml * (edit) tika-core/src/test/java/org/apache/tika/parser/mock/MockParser.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/fsshttpb/streamobj/DataElement.java * (edit) tika-batch/src/main/java/org/apache/tika/util/ClassLoaderUtil.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/fsshttpb/streamobj/basic/ExGuid.java * (edit) tika-core/src/main/java/org/apache/tika/utils/ServiceLoaderUtils.java * (edit) tika-xmp/src/test/java/org/apache/tika/xmp/XMPMetadataTest.java * (edit) tika-eval/tika-eval-core/src/test/java/org/apache/tika/eval/core/tokens/TokenCounterTest.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/onenote/fsshttpb/streamobj/basic/BasicObject.java * (edit) CHANGES.txt * (edit) tika-core/src/main/java/org/apache/tika/fork/ClassLoaderProxy.java * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-text-module/src/test/java/org/apache/tika/parser/csv/CSVSnifferTest.java > Bump main to java 11 > > > Key: TIKA-4128 > URL: https://issues.apache.org/jira/browse/TIKA-4128 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > Aside from setting maven compiler plugin's release to 11, there are a > smattering of other fixes/updates we need to make. > There are quite a few checkstyle issues for deprecated API calls, mostly > around newInstance(). > We need to delete our java 8 github workflow. > There are a couple of other things we'll want to update as well on other > tickets (jakarta and dependencies that require > 8). > This ticket just gets us started into Java 11 on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-3641) Upgrade to Lucene 9.x
[
https://issues.apache.org/jira/browse/TIKA-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3641.
---
Fix Version/s: 3.0.0-BETA
Resolution: Fixed
> Upgrade to Lucene 9.x
> -
>
> Key: TIKA-3641
> URL: https://issues.apache.org/jira/browse/TIKA-3641
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Minor
> Fix For: 3.0.0-BETA
>
>
> This is a non-trivial upgrade. I don't think it will buy us much, but we
> should do it in our {{main}} branch at some point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (TIKA-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764847#comment-17764847 ] Tim Allison commented on TIKA-4129: --- I did find in OpenNLP's release discussion that they intended to move to Java 17 in 2.3.0. This was not an accident like with mime4j. > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Fix For: 3.0.0-BETA > > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4129. --- Fix Version/s: 3.0.0-BETA Resolution: Fixed > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Fix For: 3.0.0-BETA > > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3641) Upgrade to Lucene 9.x
[
https://issues.apache.org/jira/browse/TIKA-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764844#comment-17764844
]
ASF GitHub Bot commented on TIKA-3641:
--
tballison merged PR #1335:
URL: https://github.com/apache/tika/pull/1335
> Upgrade to Lucene 9.x
> -
>
> Key: TIKA-3641
> URL: https://issues.apache.org/jira/browse/TIKA-3641
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Minor
>
> This is a non-trivial upgrade. I don't think it will buy us much, but we
> should do it in our {{main}} branch at some point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (TIKA-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764845#comment-17764845 ] ASF GitHub Bot commented on TIKA-4129: -- tballison merged PR #1336: URL: https://github.com/apache/tika/pull/1336 > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison merged pull request #1336: TIKA-4129 -- upgrade dependencies that require java 11.
tballison merged PR #1336: URL: https://github.com/apache/tika/pull/1336 -- 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 merged pull request #1335: TIKA-3641 -- upgrade Lucene to 9.x now that we're on Java 11
tballison merged PR #1335: URL: https://github.com/apache/tika/pull/1335 -- 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
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction. Is it worth pushing this modernization further or faster, with either: a) Jump to Java 17 now and keep Java 8 in 2.x for one more year b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer? Thank you, all, for your feedback! Best, Tim
[jira] [Commented] (TIKA-3641) Upgrade to Lucene 9.x
[
https://issues.apache.org/jira/browse/TIKA-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764832#comment-17764832
]
ASF GitHub Bot commented on TIKA-3641:
--
tballison opened a new pull request, #1335:
URL: https://github.com/apache/tika/pull/1335
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!
> Upgrade to Lucene 9.x
> -
>
> Key: TIKA-3641
> URL: https://issues.apache.org/jira/browse/TIKA-3641
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Minor
>
> This is a non-trivial upgrade. I don't think it will buy us much, but we
> should do it in our {{main}} branch at some point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1335: TIKA-3641 -- upgrade Lucene to 9.x now that we're on Java 11
tballison opened a new pull request, #1335: URL: https://github.com/apache/tika/pull/1335 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-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764834#comment-17764834 ] ASF GitHub Bot commented on TIKA-4129: -- tballison opened a new pull request, #1336: URL: https://github.com/apache/tika/pull/1336 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! > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1336: TIKA-4129 -- upgrade dependencies that require java 11.
tballison opened a new pull request, #1336: URL: https://github.com/apache/tika/pull/1336 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-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764830#comment-17764830 ] Tim Allison commented on TIKA-4129: --- Looks like ApacheOpenNLP 2.3.0 requires Java 17?! That was fast... :P We can at least upgrade to 2.2.0. > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-4129) Upgrade dependencies requiring > Java 8
Tim Allison created TIKA-4129: - Summary: Upgrade dependencies requiring > Java 8 Key: TIKA-4129 URL: https://issues.apache.org/jira/browse/TIKA-4129 Project: Tika Issue Type: Task Reporter: Tim Allison On TIKA-3735, we documented several dependencies that required > Java 8. Now that we're working with Java 11 on main, let's make those upgrades. There was already a separate ticket open for Lucene (TIKA-3641), so let's upgrade these: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TIKA-4129) Upgrade dependencies requiring > Java 8
[ https://issues.apache.org/jira/browse/TIKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-4129: -- Description: On TIKA-3735, we documented several dependencies that required > Java 8. Now that we're working with Java 11 on main, let's make those upgrades. There was already a separate ticket open for Lucene (TIKA-3641), so let's upgrade these: * Apache OpenNLP 2.0.0 requires Java 11. * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 * Fakeload * [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] * errorprone requires Java 11 for the build (doesn't mean we can't target 8) was: On TIKA-3735, we documented several dependencies that required > Java 8. Now that we're working with Java 11 on main, let's make those upgrades. There was already a separate ticket open for Lucene (TIKA-3641), so let's upgrade these: > Upgrade dependencies requiring > Java 8 > --- > > Key: TIKA-4129 > URL: https://issues.apache.org/jira/browse/TIKA-4129 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > On TIKA-3735, we documented several dependencies that required > Java 8. Now > that we're working with Java 11 on main, let's make those upgrades. > There was already a separate ticket open for Lucene (TIKA-3641), so let's > upgrade these: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (TIKA-3735) Require Java 11 for 2.x at some point
[ https://issues.apache.org/jira/browse/TIKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764822#comment-17764822 ] Tim Allison edited comment on TIKA-3735 at 9/13/23 6:30 PM: See TIKA-3948 and TIKA-4128 was (Author: talli...@mitre.org): See TIKA-3948 > Require Java 11 for 2.x at some point > - > > Key: TIKA-3735 > URL: https://issues.apache.org/jira/browse/TIKA-3735 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > This follows on from discussion we had on the user/dev list for when we want > to require Java 11. I think the consensus was: wait until we have to. > The following libraries require > Java 8 at the moment. I don't think > updating any of these is critical, but I do want to document where we're > stuck. > We can modify/edit this list as necessary: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Lucene 9.x – used in tika-eval > * icu4j – we can't upgrade past 62.2 (April 2019) because that is the latest > version that is compatible with Lucene 8.11.1 > ([https://github.com/apache/tika/pull/587]) > * mime4j – the last 2 (or three?) releases have been accidentally built with > Java 9 without the correct release=8. This should be fixed in the next > release. > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) > Bug fixes > * This is a profoundly stupid bug in jdk8 but not in jdk 11: > [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8213470]. I ran > into this when trying to upgrade mime4j. The problem is that > DateTimeFormatter's withZone() does a blanket override in jdk8 of the > timezone no matter if an offset was parsed in the input string. JDK11 > respects the offset correctly. Input: "Tue, 9 Jun 2009 23:58:45 -0400", > WRONG JDK 8 output:"2009-06-09T23:58:45Z" CORRECT JDK 11 output: > "2009-06-10T03:58:45Z" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764824#comment-17764824 ] Tim Allison commented on TIKA-3948: --- I renamed this issue to focus on the javax->jakarta move. The new branch -> Java 11 is now dealt with via TIKA-4128 > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-3735) Require Java 11 for 2.x at some point
[ https://issues.apache.org/jira/browse/TIKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-3735. --- Resolution: Won't Fix See TIKA-3948 > Require Java 11 for 2.x at some point > - > > Key: TIKA-3735 > URL: https://issues.apache.org/jira/browse/TIKA-3735 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > This follows on from discussion we had on the user/dev list for when we want > to require Java 11. I think the consensus was: wait until we have to. > The following libraries require > Java 8 at the moment. I don't think > updating any of these is critical, but I do want to document where we're > stuck. > We can modify/edit this list as necessary: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Lucene 9.x – used in tika-eval > * icu4j – we can't upgrade past 62.2 (April 2019) because that is the latest > version that is compatible with Lucene 8.11.1 > ([https://github.com/apache/tika/pull/587]) > * mime4j – the last 2 (or three?) releases have been accidentally built with > Java 9 without the correct release=8. This should be fixed in the next > release. > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) > Bug fixes > * This is a profoundly stupid bug in jdk8 but not in jdk 11: > [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8213470]. I ran > into this when trying to upgrade mime4j. The problem is that > DateTimeFormatter's withZone() does a blanket override in jdk8 of the > timezone no matter if an offset was parsed in the input string. JDK11 > respects the offset correctly. Input: "Tue, 9 Jun 2009 23:58:45 -0400", > WRONG JDK 8 output:"2009-06-09T23:58:45Z" CORRECT JDK 11 output: > "2009-06-10T03:58:45Z" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TIKA-3948) Migrate to jakarta in Tika 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-3948: -- Summary: Migrate to jakarta in Tika 3.x (was: Require Java 11 in 3.x) > Migrate to jakarta in Tika 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4128) Bump main to java 11
[ https://issues.apache.org/jira/browse/TIKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764812#comment-17764812 ] ASF GitHub Bot commented on TIKA-4128: -- tballison merged PR #1334: URL: https://github.com/apache/tika/pull/1334 > Bump main to java 11 > > > Key: TIKA-4128 > URL: https://issues.apache.org/jira/browse/TIKA-4128 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > Aside from setting maven compiler plugin's release to 11, there are a > smattering of other fixes/updates we need to make. > There are quite a few checkstyle issues for deprecated API calls, mostly > around newInstance(). > We need to delete our java 8 github workflow. > There are a couple of other things we'll want to update as well on other > tickets (jakarta and dependencies that require > 8). > This ticket just gets us started into Java 11 on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison merged pull request #1334: TIKA-4128 -- bump to Java 11
tballison merged PR #1334: URL: https://github.com/apache/tika/pull/1334 -- 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-4128) Bump main to java 11
[ https://issues.apache.org/jira/browse/TIKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764789#comment-17764789 ] ASF GitHub Bot commented on TIKA-4128: -- tballison opened a new pull request, #1334: URL: https://github.com/apache/tika/pull/1334 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! > Bump main to java 11 > > > Key: TIKA-4128 > URL: https://issues.apache.org/jira/browse/TIKA-4128 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > Aside from setting maven compiler plugin's release to 11, there are a > smattering of other fixes/updates we need to make. > There are quite a few checkstyle issues for deprecated API calls, mostly > around newInstance(). > We need to delete our java 8 github workflow. > There are a couple of other things we'll want to update as well on other > tickets (jakarta and dependencies that require > 8). > This ticket just gets us started into Java 11 on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1334: TIKA-4128 -- bump to Java 11
tballison opened a new pull request, #1334: URL: https://github.com/apache/tika/pull/1334 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-4128) Bump main to java 11
Tim Allison created TIKA-4128: - Summary: Bump main to java 11 Key: TIKA-4128 URL: https://issues.apache.org/jira/browse/TIKA-4128 Project: Tika Issue Type: Task Reporter: Tim Allison Aside from setting maven compiler plugin's release to 11, there are a smattering of other fixes/updates we need to make. There are quite a few checkstyle issues for deprecated API calls, mostly around newInstance(). We need to delete our java 8 github workflow. There are a couple of other things we'll want to update as well on other tickets (jakarta and dependencies that require > 8). This ticket just gets us started into Java 11 on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Let's move forth! dual branches for now: main and branch_2x https://issues.apache.org/jira/browse/TIKA-4127 On Wed, Sep 13, 2023 at 9:03 AM Maxim Solodovnik wrote: > Hello, > > from mobile (sorry for typos ;) > > > On Wed, Sep 13, 2023, 11:28 Adam Rauch wrote: > >> +1 on requiring Java 11... no problem there. >> >> Can you clarify what exactly "require jakarta" means? Tika will link to >> dependencies that happen use jakarta package names, but will have no >> problem running in a javax container (such as Tomcat 9.0.x) with javax >> libraries present? Or something else? >> > > As per my understanding Tika depends on CXF+Spring > Not sure if these two will work with their previous versions that might > present in webapp . > > Adam >> On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote: >> >> +1 from our side, we moved to java 11 last year. >> >> Best, >> Luis >> >> >> Em ter, 12 de set de 2023 19:01, Ken Krugler >> escreveu: >> >>> +1 >>> >>> On Sep 12, 2023, at 7:56 AM, Tim Allison wrote: >>> >>> Sorry, let me try that again. >>> >>> The proposal: >>> 1) start parallel main (3.x) and branch_2x branches now. >>> 2) cut a first release of 3.0.0 by the end of September (maybe October) >>> of 2023 >>> 3) Set the EOL for the 2.x branch one year after the first release of >>> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first >>> release of 3.0.0? >>> >>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other >>> major changes. >>> >>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison >>> wrote: >>> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :))) Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024? >>> -- >>> Ken Krugler >>> http://www.scaleunlimited.com >>> Custom big data solutions >>> Flink, Pinot, Solr, Elasticsearch >>> >>> >>> >>>
[jira] [Resolved] (TIKA-4127) Create branch_2x and use main for 3.x development
[ https://issues.apache.org/jira/browse/TIKA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4127. --- Resolution: Fixed > Create branch_2x and use main for 3.x development > - > > Key: TIKA-4127 > URL: https://issues.apache.org/jira/browse/TIKA-4127 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > Given feedback on the user/dev lists about moving to Java 3 in Tika 3.x, I > think we should move forth. > Let's fork "main" into branch_2x so that we can maintain our 2x for a year > and start releasing 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4127) Create branch_2x and use main for 3.x development
[
https://issues.apache.org/jira/browse/TIKA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764746#comment-17764746
]
Tim Allison commented on TIKA-4127:
---
cc [~solomax]... {{main}} awaits you! :D
> Create branch_2x and use main for 3.x development
> -
>
> Key: TIKA-4127
> URL: https://issues.apache.org/jira/browse/TIKA-4127
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Major
>
> Given feedback on the user/dev lists about moving to Java 3 in Tika 3.x, I
> think we should move forth.
> Let's fork "main" into branch_2x so that we can maintain our 2x for a year
> and start releasing 3.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (TIKA-4127) Create branch_2x and use main for 3.x development
[
https://issues.apache.org/jira/browse/TIKA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764745#comment-17764745
]
Tim Allison edited comment on TIKA-4127 at 9/13/23 3:28 PM:
I've renamed the {{2.x}} branch to {{deprecated_2.x_dev}} so that it is not
confused with {{branch_2x}}.
was (Author: talli...@mitre.org):
I've renamed {{2.x}} to {{deprecated_2.x_dev}} so that it is not confused with
{{branch_2x}}.
> Create branch_2x and use main for 3.x development
> -
>
> Key: TIKA-4127
> URL: https://issues.apache.org/jira/browse/TIKA-4127
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Major
>
> Given feedback on the user/dev lists about moving to Java 3 in Tika 3.x, I
> think we should move forth.
> Let's fork "main" into branch_2x so that we can maintain our 2x for a year
> and start releasing 3.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (TIKA-4127) Create branch_2x and use main for 3.x development
Tim Allison created TIKA-4127: - Summary: Create branch_2x and use main for 3.x development Key: TIKA-4127 URL: https://issues.apache.org/jira/browse/TIKA-4127 Project: Tika Issue Type: Task Reporter: Tim Allison Given feedback on the user/dev lists about moving to Java 3 in Tika 3.x, I think we should move forth. Let's fork "main" into branch_2x so that we can maintain our 2x for a year and start releasing 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4127) Create branch_2x and use main for 3.x development
[
https://issues.apache.org/jira/browse/TIKA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764745#comment-17764745
]
Tim Allison commented on TIKA-4127:
---
I've renamed {{2.x}} to {{deprecated_2.x_dev}} so that it is not confused with
{{branch_2x}}.
> Create branch_2x and use main for 3.x development
> -
>
> Key: TIKA-4127
> URL: https://issues.apache.org/jira/browse/TIKA-4127
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Major
>
> Given feedback on the user/dev lists about moving to Java 3 in Tika 3.x, I
> think we should move forth.
> Let's fork "main" into branch_2x so that we can maintain our 2x for a year
> and start releasing 3.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Hello, from mobile (sorry for typos ;) On Wed, Sep 13, 2023, 11:28 Adam Rauch wrote: > +1 on requiring Java 11... no problem there. > > Can you clarify what exactly "require jakarta" means? Tika will link to > dependencies that happen use jakarta package names, but will have no > problem running in a javax container (such as Tomcat 9.0.x) with javax > libraries present? Or something else? > As per my understanding Tika depends on CXF+Spring Not sure if these two will work with their previous versions that might present in webapp . Adam > On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote: > > +1 from our side, we moved to java 11 last year. > > Best, > Luis > > > Em ter, 12 de set de 2023 19:01, Ken Krugler > escreveu: > >> +1 >> >> On Sep 12, 2023, at 7:56 AM, Tim Allison wrote: >> >> Sorry, let me try that again. >> >> The proposal: >> 1) start parallel main (3.x) and branch_2x branches now. >> 2) cut a first release of 3.0.0 by the end of September (maybe October) >> of 2023 >> 3) Set the EOL for the 2.x branch one year after the first release of >> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first >> release of 3.0.0? >> >> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other >> major changes. >> >> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison wrote: >> >>> >If Tika users will be happy to move on and drop Java 8 and/or javax. >>> Please drop them :))) >>> >>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x >>> and dropping support for Java 8 and javax in September 2024? >>> >>> >> -- >> Ken Krugler >> http://www.scaleunlimited.com >> Custom big data solutions >> Flink, Pinot, Solr, Elasticsearch >> >> >> >>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
+1 on requiring Java 11... no problem there. Can you clarify what exactly "require jakarta" means? Tika will link to dependencies that happen use jakarta package names, but will have no problem running in a javax container (such as Tomcat 9.0.x) with javax libraries present? Or something else? Thanks, Adam On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote: +1 from our side, we moved to java 11 last year. Best, Luis Em ter, 12 de set de 2023 19:01, Ken Krugler escreveu: +1 On Sep 12, 2023, at 7:56 AM, Tim Allison wrote: Sorry, let me try that again. The proposal: 1) start parallel main (3.x) and branch_2x branches now. 2) cut a first release of 3.0.0 by the end of September (maybe October) of 2023 3) Set the EOL for the 2.x branch one year after the first release of 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first release of 3.0.0? In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other major changes. On Tue, Sep 12, 2023 at 10:49 AM Tim Allison wrote: >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :))) Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024? -- Ken Krugler http://www.scaleunlimited.com Custom big data solutions Flink, Pinot, Solr, Elasticsearch
[GitHub] [tika] THausherr merged pull request #1332: Bump io.projectreactor:reactor-core from 3.5.9 to 3.5.10
THausherr merged PR #1332: URL: https://github.com/apache/tika/pull/1332 -- 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 #1333: Bump reactor.netty.version from 1.1.10 to 1.1.11
THausherr merged PR #1333: URL: https://github.com/apache/tika/pull/1333 -- 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, #1333: Bump reactor.netty.version from 1.1.10 to 1.1.11
dependabot[bot] opened a new pull request, #1333: URL: https://github.com/apache/tika/pull/1333 Bumps `reactor.netty.version` from 1.1.10 to 1.1.11. Updates `io.projectreactor.netty:reactor-netty-core` from 1.1.10 to 1.1.11 Release notes Sourced from https://github.com/reactor/reactor-netty/releases;>io.projectreactor.netty:reactor-netty-core's releases. v1.1.11 Reactor Netty 1.1.11 is part of 2022.0.11 Release Train. This is a recommended update for all Reactor Netty 1.1.x users. What's Changed :sparkles: New features and improvements Depend on Reactor Core v3.5.10 by https://github.com/chemicL;>@chemicL in 6874a8f82d2e913af3790b53685ec187fc969578, see https://github.com/reactor/reactor-core/releases/tag/v3.5.10;>release notes Depend on Netty v4.1.97.Final by https://github.com/violetagg;>@violetagg in https://redirect.github.com/reactor/reactor-netty/issues/2886;>#2886 Depend on Netty QUIC Codec v0.0.50.Final by https://github.com/violetagg;>@violetagg in https://redirect.github.com/reactor/reactor-netty/issues/2888;>#2888 Depend on netty-incubator-transport-native-io_uring v0.0.22.Final by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2889;>#2889 :book: Documentation, Tests and Build Add a http snoop server sample by https://github.com/longkunbetter;>@longkunbetter in https://redirect.github.com/reactor/reactor-netty/issues/2883;>#2883 Adapt SslProviderTests to a change in Netty SNAPSHOT by https://github.com/violetagg;>@violetagg in https://redirect.github.com/reactor/reactor-netty/issues/2887;>#2887 Fix flaky test by https://github.com/violetagg;>@violetagg in https://redirect.github.com/reactor/reactor-netty/issues/2892;>#2892 :up: Build/Test Dependency Upgrades Bump de.undercouch.download to version 5.5.0 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2880;>#2880 Bump tomcat-embed-core to version 9.0.80 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2881;>#2881 Bump actions/checkout to version 4 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2894;>#2894 Bump build-info-extractor-gradle to version 4.33.5 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2896;>#2896 Bump org.gradle.test-retry to version 1.5.5 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/reactor/reactor-netty/issues/2897;>#2897 New Contributors https://github.com/longkunbetter;>@longkunbetter made their first contribution in https://redirect.github.com/reactor/reactor-netty/issues/2883;>#2883 Full Changelog: https://github.com/reactor/reactor-netty/compare/v1.1.10...v1.1.11;>https://github.com/reactor/reactor-netty/compare/v1.1.10...v1.1.11 Commits https://github.com/reactor/reactor-netty/commit/6874a8f82d2e913af3790b53685ec187fc969578;>6874a8f [release] Prepare and release 1.1.11 https://github.com/reactor/reactor-netty/commit/707a3a3069c28ca66ab22178f1d3226396ff9ece;>707a3a3 Merge-ignore 1.0.36 into 1.1.11 https://github.com/reactor/reactor-netty/commit/f4102915b280a7f493cb16f2b1e42e76bfebeea3;>f410291 [release] Back to snapshots, next is 1.0.37-SNAPSHOT https://github.com/reactor/reactor-netty/commit/8cb449051464ba48407ddcf0d334563a1ab7f4c7;>8cb4490 [release] Prepare and release 1.0.36 https://github.com/reactor/reactor-netty/commit/038d574569a99ce49d036d93c4b5db5bcdd48354;>038d574 Merge https://redirect.github.com/reactor/reactor-netty/issues/2897;>#2897 into 1.1.11 https://github.com/reactor/reactor-netty/commit/b1a941a17e1a5b6f586465cc8cb001f8606f5e8f;>b1a941a Bump org.gradle.test-retry from 1.5.4 to 1.5.5 (https://redirect.github.com/reactor/reactor-netty/issues/2897;>#2897) https://github.com/reactor/reactor-netty/commit/5a3fc4a03003d2ba51b6b07e7413294dcf56f068;>5a3fc4a Merge https://redirect.github.com/reactor/reactor-netty/issues/2896;>#2896 into 1.1.11 https://github.com/reactor/reactor-netty/commit/ea88d060f60a7282af0857fd4faf7ce5af073290;>ea88d06 Bump org.jfrog.buildinfo:build-info-extractor-gradle (https://redirect.github.com/reactor/reactor-netty/issues/2896;>#2896) https://github.com/reactor/reactor-netty/commit/649c5f1c375a619dffae01210d9d96f07f285ed4;>649c5f1 Merge https://redirect.github.com/reactor/reactor-netty/issues/2894;>#2894 into 1.1.11 https://github.com/reactor/reactor-netty/commit/231c37623d30455c583ff1523c3ad897b98dcbbb;>231c376 Bump actions/checkout from 3 to 4 (https://redirect.github.com/reactor/reactor-netty/issues/2894;>#2894) Additional commits viewable in https://github.com/reactor/reactor-netty/compare/v1.1.10...v1.1.11;>compare view Updates
[GitHub] [tika] dependabot[bot] opened a new pull request, #1332: Bump io.projectreactor:reactor-core from 3.5.9 to 3.5.10
dependabot[bot] opened a new pull request, #1332: URL: https://github.com/apache/tika/pull/1332 Bumps [io.projectreactor:reactor-core](https://github.com/reactor/reactor-core) from 3.5.9 to 3.5.10. Commits https://github.com/reactor/reactor-core/commit/7f9c77ec28dc0bdfc1eafe04062cb1195fd9b552;>7f9c77e [release] Prepare and release 3.5.10 https://github.com/reactor/reactor-core/commit/8d33a1d9870a6f1a15091f6d0e674af6677ce985;>8d33a1d Merge branch '3.4.x' into 3.5.10 https://github.com/reactor/reactor-core/commit/0daeb537b1731c4cd37d2a33a5ceb852e4f13cbb;>0daeb53 Revert [release] Prepare and release 3.4.33 https://github.com/reactor/reactor-core/commit/db218a9c34ca6d9c706ba4c9ab6bb343bb7dc6be;>db218a9 [release] Prepare and release 3.4.33 https://github.com/reactor/reactor-core/commit/9dabc1374be09ddc126c0224020d2880ac97d7d8;>9dabc13 fixes return type for Mono.tap in javadoc (https://redirect.github.com/reactor/reactor-core/issues/3564;>#3564) https://github.com/reactor/reactor-core/commit/984c4eb4b4e9da103e1fec84abe4c0e0ae47254b;>984c4eb Update context propagation to 1.0.5 https://github.com/reactor/reactor-core/commit/086c0edbeff3fc093be153b4df9903e6f6ec6f98;>086c0ed [release] Next development version 3.5.10-SNAPSHOT See full diff in https://github.com/reactor/reactor-core/compare/v3.5.9...v3.5.10;>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] THausherr merged pull request #1331: Bump aws.version from 1.12.548 to 1.12.549
THausherr merged PR #1331: URL: https://github.com/apache/tika/pull/1331 -- 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
