[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

configuration to get more information. > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/browse/TIKA-2676 >

[jira] [Comment Edited] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

getting that exception?   :D  I don't think that could come from our code...I could be wrong was (Author: talli...@mitre.org): Then how are you getting that exception?!  !/jira/images/icons/emoticons/tongue.png|width=16,height=16!   :D > After switching to TIKA 1.18 from 1.17 started to

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

. As far as I know.  > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/browse/TIKA-2676 >

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

ActivationDataFlavor? > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/browse/TIKA-2676 >

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

and content type.   As for 1.19 - will try on it :)   Thanks > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/j

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

tests run multi-threaded on a single parser. > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/b

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

more information soon.  Question are AutoDetectParser and other TIKA parsers in general are thread-safe ? as it could be that we have about 15 threads that each of then will have its own Parser Thanks fro your help, really appreciate that !!! Slava.   > After switching to TIKA 1.18 from 1

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

ou passing in, e.g., Metadata.Content_Type, and that is somehow corrupted?   > After switching to TIKA 1.18 from 1.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.ap

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

And maybe I mislead you, we're taking from emails mimparts and passing for parsing to TIKA only strings, so It's kind "fake" mail parsing. But, maybe another binary is making problems here , but still can figure it out who is troublemaker. > After switching to TIKA 1.18 from 1.17 s

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

" that's _some_ information at least.  Once, when I upgraded Tika for Solr, I forgot to upgrade mime4j, and there was a binary incompatibility:  SOLR-11622.  Perhaps you have an old version of mime4j somewhere on your classpath? > After switching to TIKA 1.18 from 1.17 started

[jira] [Commented] (TIKA-2716) Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable

dependency tree now (see TIKA-2721) > Sonatype Nexus auditor is reporting that spring framework vesrion used by > Tika 1.18 is vulnerable > - > > Key: TIKA-2716 >

[jira] [Closed] (TIKA-2716) Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable

2.0 > Sonatype Nexus auditor is reporting that spring framework vesrion used by > Tika 1.18 is vulnerable > - > > Key: TIKA-2716 >

[jira] [Created] (TIKA-2716) Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable

Abhijit Rajwade created TIKA-2716: - Summary: Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable Key: TIKA-2716 URL: https://issues.apache.org/jira/browse/TIKA-2716

[jira] [Updated] (TIKA-2676) After switching to TIKA 1.18 from 1.17 started to get exception

[ https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slava G updated TIKA-2676: -- Summary: After switching to TIKA 1.18 from 1.17 started to get exception (was: After switching to TIKA 1.18

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from !.17 started to get exception

workstations or even in AWS cloud it's almost not possible to reproduce, I know it's sound very strange, sorry about that but this is currently the situation, our dev team is trying to  identify the issue  and reproduce it, but it could take some time. Thanks. > After switching to TIKA 1.18 from !

[jira] [Updated] (TIKA-2676) After switching to TIKA 1.18 from !.17 started to get exception

[ https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slava G updated TIKA-2676: -- Description: I recently switched from TIKA 1.17 to TIKA 1.18 (I'm using tika to parse emails). And I started

[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from !.17 started to get exception

?  The only place we use DataFlavor is in our gui. > After switching to TIKA 1.18 from !.17 started to get exception > --- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/b

[jira] [Created] (TIKA-2676) After switching to TIKA 1.18 from !.17 started to get exception

Slava G created TIKA-2676: - Summary: After switching to TIKA 1.18 from !.17 started to get exception Key: TIKA-2676 URL: https://issues.apache.org/jira/browse/TIKA-2676 Project: Tika Issue Type

Fwd: [ANNOUNCE] Apache Tika 1.18 released

The Apache Tika project is pleased to announce the release of Apache Tika 1.18. The release contents have been pushed out to the main Apache release site and to the Maven Central sync, so the releases should be available as soon as the mirrors get the syncs. Apache Tika is a toolkit

[RESULT] [VOTE] Release Apache Tika 1.18 Candidate #3

: Re: [VOTE] Release Apache Tika 1.18 Candidate #3   Hi Tim   It looks like something to do with my Tesseract setup on my Mac     It is all working perfectly on my Windows and Linux machines, so +1 from me on the release too.   Cheers, Dave   On 24 April 2018 at 13

Re: [VOTE] Release Apache Tika 1.18 Candidate #3

e [mailto:loo...@gmail.com] > Sent: Monday, April 23, 2018 7:07 PM > To: dev@tika.apache.org > Subject: Re: [VOTE] Release Apache Tika 1.18 Candidate #3 > > Hey Tim, > > Just started looking at this and got an error with Tesseract enabled. Will > try to see if it is

RE: [VOTE] Release Apache Tika 1.18 Candidate #3

:07 PM To: dev@tika.apache.org Subject: Re: [VOTE] Release Apache Tika 1.18 Candidate #3 Hey Tim, Just started looking at this and got an error with Tesseract enabled. Will try to see if it is localised to me or not. Cheers, Dave On 22 April 2018 at 13:29, Oleg Tikhonov <o...@apache.org>

Re: [VOTE] Release Apache Tika 1.18 Candidate #3

PM, Oleg Tikhonov <o...@apache.org> wrote: > >> My bad. This one, hopefully ... >> >> >> On Sun, Apr 22, 2018 at 3:01 PM, Oleg Tikhonov <o...@apache.org> wrote: >> >>> Hi, >>> thanks a lot. >>> [x] +1 Release this package a

Re: [VOTE] Release Apache Tika 1.18 Candidate #3

Hi, thanks a lot. [x] +1 Release this package as Apache Tika 1.18 Even did a security scan: mvn org.owasp:dependency-check-maven:3.1.2:check Report is attached. Best regards, Oleg On Sat, Apr 21, 2018 at 12:54 AM, talli...@apache.org <talli...@apache.org> wrote: > All, >

[VOTE] Release Apache Tika 1.18 Candidate #3

All, A candidate for the Tika 1.18 release is available at:    https://dist.apache.org/repos/dist/dev/tika/ The release candidate is a zip archive of the sources in:    https://github.com/apache/tika/tree/1.18-rc3 The SHA-512 checksum of the archive

Re: [VOTE][CANCELLED] Release Apache Tika 1.18 Candidate #2

Cancelling vote because of TIKA-2634. Will respin RC3 shortly. On Monday, April 16, 2018, 9:32:06 PM EDT, Tim Allison <talli...@apache.org> wrote: A candidate for the Tika 1.18 release is available at:  https://dist.apache.org/repos/dist/dev/tika/ The release candidate is a zip a

[VOTE] Release Apache Tika 1.18 Candidate #2

A candidate for the Tika 1.18 release is available at:  https://dist.apache.org/repos/dist/dev/tika/ The release candidate is a zip archive of the sources in:  https://github.com/apache/tika/tree/1.18-rc2/ The SHA-512 checksum of the archive

Re: [VOTE] Release Apache Tika 1.18 Candidate #1

[+] Release this package as Apache Tika 1.18 [INFO] Apache Tika parent . SUCCESS [ 12.379 s] [INFO] Apache Tika core ... SUCCESS [ 55.650 s] [INFO] Apache Tika parsers SUCCESS [05:55 min] [INFO

[VOTE] Release Apache Tika 1.18 Candidate #1

A candidate for the Tika 1.18 release is available at:   https://dist.apache.org/repos/dist/dev/tika/ The release candidate is a zip archive of the sources in:   https://github.com/apache/tika/tree/1.18-rc1/ The SHA-512 checksum of the archive

RE: Tika 1.18?

On Mon, 12 Mar 2018, Allison, Timothy B. wrote: Anyone have anything they'd like to get in before I run the regression tests? I can certainly put it off a few days. I've made some progress on the metadata-only fallback/merge multiple parser work from

RE: Tika 1.18?

, Tim -Original Message- From: Chris Mattmann [mailto:mattm...@apache.org] Sent: Wednesday, March 7, 2018 4:57 PM To: dev@tika.apache.org Subject: Re: Tika 1.18? Sounds good to me thanks Tim. Happy to line it up with PDF Box 2.0.9

Re: Tika 1.18?

Sounds good to me thanks Tim. Happy to line it up with PDF Box 2.0.9 On 3/7/18, 1:16 PM, "Allison, Timothy B." wrote: All, I think I've made the updates that I wanted to make sure got in to 1.18. It looks like PDFBox is going to start their release cycle

RE: Tika 1.18?

All, I think I've made the updates that I wanted to make sure got in to 1.18. It looks like PDFBox is going to start their release cycle shortly. Should we wait for PDFBox 2.0.9? That may add a week or two to our release, although, frankly, it might not. We can start running the

Re: Tika 1.18?

I thought about logging any custom-mimetype override applied, so the user will be warned about that. Maybe additionally creating a specific attribute in mimetype definition xml to configure it must override the default one instead of aborting. About multiple conflicting custom mimes from different

Re: Tika 1.18?

On Fri, 2 Mar 2018, Luís Filipe Nassif wrote: If I make no progress on TIKA-1466 until 3/9, you can start the release process without it. But do you devs agree with the proposed change: allow overriding of glob patterns in custom-mimetypes.xml? What happens if you have two different custom

RE: Tika 1.18?

Subject: Re: Tika 1.18? If I make no progress on TIKA-1466 until 3/9, you can start the release process without it. But do you devs agree with the proposed change: allow overriding of glob patterns in custom-mimetypes.xml?

RE: Tika 1.18?

TIKA-2591 and TIKA-2568 +1 TIKA-1466 -- how long will it take, do you think? This seems potentially non-trivial... -Original Message- From: Luís Filipe Nassif [mailto:lfcnas...@gmail.com] Sent: Thursday, March 1, 2018 5:41 PM To: dev@tika.apache.org Subject: Re: Tika 1.18? I think we

Re: Tika 1.18?

I think we should workaround TIKA-2591, and I would like to work on TIKA-1466 (what do you think?) and fix TIKA-2568. Cheers, Luis Livre de vírus. www.avast.com

Re: Tika 1.18?

Same: makes perfect sense to me and let's do it ( I just updated (finally) Tika Python down stream to be based on the 1.16 Tika, I guess I should get it based on 1.17 soon too ( https://github.com/chrismattmann/tika-python/blob/master/tika/__init__.py#L17 Cheers, Chris On 3/1/18, 5:16 AM,

Re: Tika 1.18?

On Thu, 1 Mar 2018, Allison, Timothy B. wrote: There have been some important bug fixes, a few new capabilities, and the upgrading of dependencies because of CVEs. There are a bunch of mime tickets from Andreas Meier that I’d like to get into 1.18. Is there anything else that is critical?

Tika 1.18?

All, There have been some important bug fixes, a few new capabilities, and the upgrading of dependencies because of CVEs. There are a bunch of mime tickets from Andreas Meier that I’d like to get into 1.18. Is there anything else that is critical? Schedule wise, I propose getting changes in