[
https://issues.apache.org/jira/browse/TIKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459670#comment-17459670
]
ASF GitHub Bot commented on TIKA-3327:
--
lewismc commented on a change in pull request
lewismc commented on a change in pull request #417:
URL: https://github.com/apache/tika/pull/417#discussion_r769277762
##
File path:
tika-server/src/main/java/org/apache/tika/server/mbean/ServerStatusExporter.java
##
@@ -0,0 +1,66 @@
+package org.apache.tika.server.mbean;
Rev
[
https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459668#comment-17459668
]
ASF GitHub Bot commented on TIKA-3353:
--
lewismc commented on a change in pull request
lewismc commented on a change in pull request #429:
URL: https://github.com/apache/tika/pull/429#discussion_r769272590
##
File path:
tika-server/src/main/java/org/apache/tika/server/metrics/ServerStatusMetrics.java
##
@@ -0,0 +1,61 @@
+/*
+ * Licensed to the Apache Software Fo
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456284#comment-17456284
]
Vamsi Molli edited comment on TIKA-3614 at 12/15/21, 5:57 AM:
--
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsi Molli closed TIKA-3614.
-
Resolution: Fixed
> Trying to upgrade from 1.27 to 2.1.0
>
>
>
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457014#comment-17457014
]
Vamsi Molli edited comment on TIKA-3614 at 12/15/21, 5:56 AM:
--
[
https://issues.apache.org/jira/browse/TIKA-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsi Molli reopened TIKA-3614:
---
> Trying to upgrade from 1.27 to 2.1.0
>
>
> Key: TIK
[
https://issues.apache.org/jira/browse/TIKA-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsi Molli closed TIKA-3615.
-
Resolution: Fixed
> Missing class file while upgrade to TIka 2.1.0
> -
[
https://issues.apache.org/jira/browse/TIKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459664#comment-17459664
]
ASF GitHub Bot commented on TIKA-3619:
--
lewismc opened a new pull request #464:
URL:
lewismc opened a new pull request #464:
URL: https://github.com/apache/tika/pull/464
This trivial issue addresses https://issues.apache.org/jira/browse/TIKA-3619
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Am 13.12.2021 um 19:05 schrieb Tim Allison:
All,
I'm currently in the process of building the rc1 for Tika 2.x. On
TIKA-3616, Luís Filipe Nassif asked if we could upgrade log4j to
log4j2 in the 1.x branch. I think we avoided that because it would be
a breaking change(?). There are security v
Hi, folks.
I'm +1 to both updating to log4j2 or logback and supporting security
updates for some time if we can but encourage migration to 2.2+ ASAP. Maybe
we should publish some EOL date in the 2.2.0 announcement if we didn't
before. It should give both time scope for migration and limit committe
Hi, folks.
Built successfully on ArchLinux, OpenJDK 11 & 17 (Temurin-11.0.13+8 &
17.0.1+12) w/ Tesseract 4.1.1, Leptonica 1.82.0 except:
*
org.apache.tika.parser.ocr.TesseractOCRParserTest.confirmMultiPageTiffHandling
(still extracts "Page?2" instead of "Page 2" on my laptop);
* bunch of potential
Sorry about the additional work, Tim. I thought upgrading from log4j-1.x to
2.x on Tika-1.x maybe could not be that hard and didn't know about breaking
changes.
Related to Eric's email, would we support Tika-1.x security updates for
some while (that was my intent with the proposal above)? Was this
Lewis John McGibbney created TIKA-3619:
--
Summary: Augment README with build prerequisites
Key: TIKA-3619
URL: https://issues.apache.org/jira/browse/TIKA-3619
Project: Tika
Issue Type: Im
+1
> On 15 Dec 2021, at 0:01, Tim Allison wrote:
>
> +1
>
> On Tue, Dec 14, 2021 at 4:31 PM Lewis John McGibbney
> wrote:
>
>> I'll submit a PR for the README but I think it's also worthwile to augment
>> the release management guide so that the message to review the release
>> candidate inc
+1
On Tue, Dec 14, 2021 at 4:31 PM Lewis John McGibbney
wrote:
> I'll submit a PR for the README but I think it's also worthwile to augment
> the release management guide so that the message to review the release
> candidate includes this information.
> lewismc
>
> On 2021/12/14 20:17:05 Tim All
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459506#comment-17459506
]
Hudson commented on TIKA-3618:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-branch1x-jd
[
https://issues.apache.org/jira/browse/TIKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459507#comment-17459507
]
Hudson commented on TIKA-3585:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-branch1x-jd
I'll submit a PR for the README but I think it's also worthwile to augment the
release management guide so that the message to review the release candidate
includes this information.
lewismc
On 2021/12/14 20:17:05 Tim Allison wrote:
> Y, you're right. Lewis, where should we mention the Docker re
As with 2.x, we can make a 1.28.1 release with the updated PDFBox
early in the new year.
On Tue, Dec 14, 2021 at 3:50 PM Tim Allison wrote:
>
> All,
> We upgraded to log4j 2.16.0 in the 1.x branch and upgraded a few
> other dependencies that ossindex flagged as vulnerable. Given the
> breaking
All,
We upgraded to log4j 2.16.0 in the 1.x branch and upgraded a few
other dependencies that ossindex flagged as vulnerable. Given the
breaking changes in migrating from log4j to log4j2, I've gone with the
notion that the next 1.x release should be 1.28, not 1.27.1.
Once Subhajit has a chance
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459463#comment-17459463
]
Tim Allison commented on TIKA-3618:
---
I just pushed the updates to the {{branch_1x}}. Pl
Y, you're right. Lewis, where should we mention the Docker requirement
on our site?
On Tue, Dec 14, 2021 at 3:06 PM Lewis John McGibbney wrote:
>
> Hi Ken,
>
> On 2021/12/13 22:38:49 Ken Krugler wrote:
> > That error looks like you’ve got a connection issue with the Maven central
> > repo…
> >
>
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459452#comment-17459452
]
Tim Allison commented on TIKA-3618:
---
Great! As long as you're ok w the change! :D
> Up
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459434#comment-17459434
]
Tim Allison edited comment on TIKA-3618 at 12/14/21, 8:06 PM:
--
Hi Ken,
On 2021/12/13 22:38:49 Ken Krugler wrote:
> That error looks like you’ve got a connection issue with the Maven central
> repo…
>
> — Ken
Yes you are correct :)
Once that issue sorted itself out my local build passed so my +1 stands.
I this it is worthwhile us stating that Docker is a
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459445#comment-17459445
]
Subhajit Das commented on TIKA-3618:
Hi [~tallison],
Yes the Log4j2 is supported out
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459434#comment-17459434
]
Tim Allison edited comment on TIKA-3618 at 12/14/21, 7:34 PM:
--
[
https://issues.apache.org/jira/browse/TIKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459434#comment-17459434
]
Tim Allison commented on TIKA-3618:
---
This is going to be majorly breaking for the microm
This is the issue solved by 2.16.0:
https://www.cve.org/CVERecord?id=CVE-2021-45046
I think that 2.15.0 is probably good enough for now. We can upgrade
to 2.16.0 in 2.2.1, when we upgrade PDFBox and POI early in the new
year.
If anyone has a technical reason to think we should respin 2.2.0-rc1,
[
https://issues.apache.org/jira/browse/TIKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459284#comment-17459284
]
ASF GitHub Bot commented on TIKA-3417:
--
wjwilson-ibm commented on pull request #4:
UR
wjwilson-ibm commented on pull request #4:
URL: https://github.com/apache/tika-docker/pull/4#issuecomment-993718392
Hi @dameikle I can confirm the image logicalspark/docker-tikaserver:1.27
changed yesterday. Thank you. Unfortunately, shelling into the running
container shows user root an
34 matches
Mail list logo
