[
https://issues.apache.org/jira/browse/TIKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389119#comment-17389119
]
Hudson commented on TIKA-3505:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #296 (See
[
https://issues.apache.org/jira/browse/TIKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389088#comment-17389088
]
Hudson commented on TIKA-3499:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk8 #295 (See
[
https://issues.apache.org/jira/browse/TIKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389087#comment-17389087
]
Hudson commented on TIKA-3505:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk8 #295 (See
[
https://issues.apache.org/jira/browse/TIKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3505.
---
Fix Version/s: 2.0.1
Assignee: Tim Allison
Resolution: Fixed
> Move
Tim Allison created TIKA-3505:
-
Summary: Move maxForEmitBatchBytes into PipesConfigBase
Key: TIKA-3505
URL: https://issues.apache.org/jira/browse/TIKA-3505
Project: Tika
Issue Type: Task
[
https://issues.apache.org/jira/browse/TIKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388902#comment-17388902
]
Hudson commented on TIKA-3502:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #294 (See
[
https://issues.apache.org/jira/browse/TIKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388901#comment-17388901
]
Hudson commented on TIKA-3499:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #294 (See
[
https://issues.apache.org/jira/browse/TIKA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-1436.
---
Fix Version/s: (was: 2.0.1)
(was: 2.0.0-BETA)
(was:
[
https://issues.apache.org/jira/browse/TIKA-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-1709:
--
Fix Version/s: (was: 2.0.1)
(was: 2.0.0-BETA)
(was:
[
https://issues.apache.org/jira/browse/TIKA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-2071:
--
Fix Version/s: (was: 2.0.1)
(was: 2.0.0-BETA)
> Tika 2.0 - DefaultParser and
Thank you, Lewis.
1. I just "released" 2.0.0-BETA on JIRA. Good catch.
2. 1.28 -- we should keep this available for parallel 1.x and 2.x
releases for a bit, I think.
3. As for the straggling issues...there are straggling issues. :D
Onwards and thank you!
On Wed, Jul 28, 2021 at 12:18 PM Lewis
However, I'm certainly open to locking down Tika as much as possible
if there are any takers...
On Wed, Jul 28, 2021 at 12:17 PM Tim Allison wrote:
>
> We haven't. Elasticsearch does this before calling Tika. Given that
> the SecurityManager is slated to be removed in a version of Java we'll
>
Hi Tim,
In short, yes :0)
A couple of questions
1. I see the 2.0.0-BETA development drive is still open in JIRA -
https://issues.apache.org/jira/projects/TIKA/versions/12350403 should this be
cleaned up/released/closed?
2. Same for 1.28?
We haven't. Elasticsearch does this before calling Tika. Given that
the SecurityManager is slated to be removed in a version of Java we'll
get to by 2030, I was hesitant.
We have to defend against oom and infinite loops; if we protected
against literal System.exit with the SecurityManager, it
Tim Allison created TIKA-3504:
-
Summary: Convert org.testcontainers in OpenSearch and Solr to
junit5
Key: TIKA-3504
URL: https://issues.apache.org/jira/browse/TIKA-3504
Project: Tika
Issue
Hi Tim,
Did we ever try this approach of catching the System.exit() call?
https://stackoverflow.com/questions/5549720/how-to-prevent-calls-to-system-exit-from-terminating-the-jvm
Though I imagine calling System.setSecurityManager() isn’t appropriate for a
library :)
— Ken
> On Jul 28, 2021,
[
https://issues.apache.org/jira/browse/TIKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388863#comment-17388863
]
Hudson commented on TIKA-3502:
--
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #293 (See
[
https://issues.apache.org/jira/browse/TIKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388854#comment-17388854
]
Hudson commented on TIKA-3502:
--
UNSTABLE: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #143 (See
Tim Allison created TIKA-3503:
-
Summary: Figure out how to upgrade dl4j
Key: TIKA-3503
URL: https://issues.apache.org/jira/browse/TIKA-3503
Project: Tika
Issue Type: Task
Reporter:
Tim,
Usually I set a SecurityManager that prevents calls to System.exit. You
will have to allow Surefire (and probably also your IDE test runner) to
allow to use System.exit.
Enrico
Il giorno mer 28 lug 2021 alle ore 16:18 Tim Allison
ha scritto:
> All,
>
> I'm trying to upgrade the surefire
All,
I'm trying to upgrade the surefire plugin in Apache Tika, and I'm
running into "forked vm terminated without properly saying goodbye"
[0].
Tika uses a bunch of dependencies we have no control over. At one
point, we had a parser with a "feature" that called System.exit. We
have code
Tim Allison created TIKA-3502:
-
Summary: General upgrades for 2.0.1
Key: TIKA-3502
URL: https://issues.apache.org/jira/browse/TIKA-3502
Project: Tika
Issue Type: Task
Reporter: Tim
+1
On Wed, Jul 28, 2021, 6:44 AM Tilman Hausherr wrote:
> +1
>
> I'm almost always pro "releasing". We'd need an issue to put stuff up to
> date, e.g. commons-io
>
> Tilman
>
> Am 26.07.2021 um 23:02 schrieb Tim Allison:
> > All,
> >We've made some important cleanups and updated some
+1
I'm almost always pro "releasing". We'd need an issue to put stuff up to
date, e.g. commons-io
Tilman
Am 26.07.2021 um 23:02 schrieb Tim Allison:
All,
We've made some important cleanups and updated some vulnerable
dependencies recently. Should we aim for August 2 or so to start the
24 matches
Mail list logo
