+1
Successful build on german W10
Tilman
Am 19.12.2021 um 19:53 schrieb Tim Allison:
A candidate for the Tika 2.2.1 release is available at:
https://dist.apache.org/repos/dist/dev/tika/2.2.1
The release candidate is a zip archive of the sources in:
https://github.com/apache/tika/tree/2.2.1-rc
[
https://issues.apache.org/jira/browse/TIKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462358#comment-17462358
]
ASF GitHub Bot commented on TIKA-3627:
--
bgeisberger opened a new pull request #467:
U
bgeisberger opened a new pull request #467:
URL: https://github.com/apache/tika/pull/467
Fixes TIKA-3627
--
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-
Bernhard Geisberger created TIKA-3627:
-
Summary: OOXML parsing is not working as intended using multiple
threads
Key: TIKA-3627
URL: https://issues.apache.org/jira/browse/TIKA-3627
Project: Tika
Great catch. Will respin 1.28 tomorrow. Thank you!
On Sun, Dec 19, 2021 at 5:33 PM Konstantin Gribov wrote:
> Built successfully on ArchLinux, OpenJDK 11 & 17 (Temurin-11.0.13+8 &
> 17.0.1+12) w/ Tesseract 4.1.1, Leptonica 1.82.
> Same issue as with 2.2.1 rc2 with tesseract multipage test.
>
> G
Built successfully on ArchLinux, OpenJDK 11 & 17 (Temurin-11.0.13+8 &
17.0.1+12) w/ Tesseract 4.1.1, Leptonica 1.82.
Same issue as with 2.2.1 rc2 with tesseract multipage test.
GPG signatures are fine, SHA512 are fine except for the absence of
tika-server-1.28-bin.tgz hashsum.
[ ] +1 Release this
Built successfully on ArchLinux, OpenJDK 11 & 17 (Temurin-11.0.13+8 &
17.0.1+12) w/ Tesseract 4.1.1, Leptonica 1.82.
Same issues with tesseract & logging deps in test scope.
Checksums and GPG signatures seem fine.
[x] +1 Release this package as Apache Tika 2.2.1
[ ] -1 Do not release this package
A candidate for the Tika 1.28 release is available at:
https://dist.apache.org/repos/dist/dev/tika/1.28
The release candidate is a zip archive of the sources in:
https://github.com/apache/tika/tree/1.28-rc2/
The SHA-512 checksum of the archive is
75aff4f61baf2dcc33126ce08b81705e5b421752993
[
https://issues.apache.org/jira/browse/TIKA-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3625:
--
Fix Version/s: 1.28
2.2.1
> Upgrade log4j to 2.17.0
> ---
>
>
tballison closed pull request #466:
URL: https://github.com/apache/tika/pull/466
--
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...@t
tballison commented on pull request #466:
URL: https://github.com/apache/tika/pull/466#issuecomment-997453587
Thank you for this. I made the upgrades before I saw your PR. I've kicked
off the release cycle for both 2.2.1-rc2 and 1.28-rc2 (well, will shortly).
--
This is an automated me
A candidate for the Tika 2.2.1 release is available at:
https://dist.apache.org/repos/dist/dev/tika/2.2.1
The release candidate is a zip archive of the sources in:
https://github.com/apache/tika/tree/2.2.1-rc2/
The SHA-512 checksum of the archive is
11daaae66bf435d84abd7e24e4c3d827438ef7517f224de
[
https://issues.apache.org/jira/browse/TIKA-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462207#comment-17462207
]
Hudson commented on TIKA-3626:
--
FAILURE: Integrated in Jenkins build Tika » tika-main-jdk8 #3
[
https://issues.apache.org/jira/browse/TIKA-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462204#comment-17462204
]
Hudson commented on TIKA-3625:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #3
All,
I'm now -1 on this given that log4j 2.17.0 is available. I'm not
that troubled by the current security vuln found in 2.16.0, but I'd
like to avoid the communications between the PMC and our community and
between our community and their security scanners about why we aren't
on 2.17.0.
I'll
All,
I'm now -1 on this given that log4j 2.17.0 is available. I'm not
that troubled by the current security vuln found in 2.16.0, but I'd
like to avoid the communications between the PMC and our community and
between our community and their security scanners about why we aren't
on 2.17.0.
I'll
Tim Allison created TIKA-3626:
-
Summary: Various upgrades for next 2.x release
Key: TIKA-3626
URL: https://issues.apache.org/jira/browse/TIKA-3626
Project: Tika
Issue Type: Task
Repor
[
https://issues.apache.org/jira/browse/TIKA-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3625.
---
Resolution: Fixed
fix versions to be updated..
> Upgrade log4j to 2.17.0
> ---
>
Tim Allison created TIKA-3625:
-
Summary: Upgrade log4j to 2.17.0
Key: TIKA-3625
URL: https://issues.apache.org/jira/browse/TIKA-3625
Project: Tika
Issue Type: Task
Reporter: Tim Allis
19 matches
Mail list logo