[
https://issues.apache.org/jira/browse/TIKA-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461768#comment-17461768
]
Tilman Hausherr commented on TIKA-3622:
---
>From the PDFBox regression test a few days ago:
Thanks Dave.
I saw https://issues.apache.org/jira/browse/INFRA-22626
Looks like Tika was suffering from the same issue.
The jar's are now available.
Thanks
On 2021/12/17 23:06:26 Dave Fisher wrote:
> Get on #afinfra in slack and look at the scroll back.
>
> > On Dec 17, 2021, at 2:59 PM, lewis
Get on #afinfra in slack and look at the scroll back.
> On Dec 17, 2021, at 2:59 PM, lewis john mcgibbney wrote:
>
> I’ve been waiting on the M2 central Repository being updated with the 2.2.0
> jars…
> I checked repository.Apache.org and they are NOT staged which I assume
> means that the
I’ve been waiting on the M2 central Repository being updated with the 2.2.0
jars…
I checked repository.Apache.org and they are NOT staged which I assume
means that the staging repository has been closed which should have
triggered the release to maven central.
Anyone know what’s going on?
lewismc
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-rc1/
The SHA-512 checksum of the archive is
[
https://issues.apache.org/jira/browse/TIKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461645#comment-17461645
]
Hudson commented on TIKA-3624:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #395 (See
[
https://issues.apache.org/jira/browse/TIKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated TIKA-3620:
---
Fix Version/s: 2.2.0
> Language detection documentation needs attention
>
[
https://issues.apache.org/jira/browse/TIKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-3620.
Resolution: Fixed
https://tika.apache.org/2.2.0/detection.html#Language_Detection
[
https://issues.apache.org/jira/browse/TIKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461618#comment-17461618
]
Lewis John McGibbney commented on TIKA-3620:
% svn ci -m "TIKA-3620 Language detection
[
https://issues.apache.org/jira/browse/TIKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461610#comment-17461610
]
Hudson commented on TIKA-3624:
--
FAILURE: Integrated in Jenkins build Tika » tika-main-jdk8 #394 (See
Maven central is having a bad week.
-- Forwarded message -
From: Tim Allison
Date: Fri, Dec 17, 2021 at 12:44 PM
Subject: [apache/tika] Run failed: main pr build - main (f87a8a1)
To: apache/tika
Cc: Ci activity
[image: GitHub] [apache/tika] main pr build workflow run
main
[
https://issues.apache.org/jira/browse/TIKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3624.
---
Fix Version/s: 2.2.1
Resolution: Fixed
We'll start the release process for 2.2.1 shortly.
Carina Antunes created TIKA-3624:
Summary: Version 2.0.0 forward breaks metadata in unpack/all
(>From 1.27)
Key: TIKA-3624
URL: https://issues.apache.org/jira/browse/TIKA-3624
Project: Tika
[
https://issues.apache.org/jira/browse/TIKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carina Antunes updated TIKA-3624:
-
Description:
In API unpack/all, metadata name keys are missing from _{_}METADATA{_}_.
Expected
It isn't. We're starting the release cycle for 2.2.1 with Log4j 2.16.0
in a few hours. Thank you for update.
On Fri, Dec 17, 2021 at 11:17 AM Cristian Zamfir wrote:
>
> Hi, is the lower priority for CVE-2021-45046 still accurate in light of this?
>
Hi, is the lower priority for CVE-2021-45046 still accurate in light of
this?
https://www.lunasec.io/docs/blog/log4j-zero-day-severity-of-cve-2021-45046-increased
On Thu, Dec 16, 2021 at 6:22 PM Tim Allison wrote:
> The recently publicized CVE-2021-44228 in log4j2 allows for
> unauthenticated
[
https://issues.apache.org/jira/browse/TIKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov updated TIKA-3623:
Priority: Blocker (was: Major)
> Upgrade log4j to 2.16.0
> ---
>
>
[
https://issues.apache.org/jira/browse/TIKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov updated TIKA-3623:
Summary: Upgrade log4j to 2.16.0 (was: Upgrade log4j to 2.0.16)
> Upgrade log4j to 2.16.0
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov updated TIKA-3616:
Summary: Upgrade log4j2 to 2.15.0 (was: Upgrade log4j2 to 2.0.15)
> Upgrade log4j2 to
Looks like things were still slow yesterday... thank you for the link!
Update - Staging operations will be paused for the next 30-45 minutes
to allow some of the backlog of staging operations to clear. Builds
that attempt to create new staging operations will throw 405 errors.
Dec 16, 20:05 EST
Hi Tamás,
I notice that Tika 2.2.0 is not in maven central now even though I
released it yesterday. I also notice that PDFBox 2.0.25 is not in
maven central even though it was released several hours ago. Is this
likely an issue with maven central or Apache's nexus repo manager?
Thank you!
[
https://issues.apache.org/jira/browse/TIKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3623.
---
Fix Version/s: 1.28
2.2.1
Resolution: Fixed
> Upgrade log4j to 2.0.16
>
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3616:
--
Priority: Blocker (was: Major)
> Upgrade log4j2 to 2.0.15
>
>
>
Tim Allison created TIKA-3623:
-
Summary: Upgrade log4j to 2.0.16
Key: TIKA-3623
URL: https://issues.apache.org/jira/browse/TIKA-3623
Project: Tika
Issue Type: Task
Reporter: Tim
[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3616:
--
Summary: Upgrade log4j2 to 2.0.15 (was: Upgrade log4j2)
> Upgrade log4j2 to 2.0.15
>
Tim Allison created TIKA-3622:
-
Summary: Upgrade pdfbox to 2.0.25
Key: TIKA-3622
URL: https://issues.apache.org/jira/browse/TIKA-3622
Project: Tika
Issue Type: Task
Reporter: Tim
[
https://issues.apache.org/jira/browse/TIKA-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3622:
--
Summary: Upgrade PDFBox to 2.0.25 (was: Upgrade pdfbox to 2.0.25)
> Upgrade PDFBox to 2.0.25
>
On Thu, Dec 16, 2021 at 1:27 PM Tim Allison wrote:
>
> Is this something worth pursuing? Are there things we can do with the
> SecurityManager or via other techniques to improve the robustness of
> our codebase?
>
Couple thoughts:
As a library, you can create a policy for tests and run your
28 matches
Mail list logo