Taken. Thanks. in progress ...
On Tue, Oct 21, 2014 at 8:54 AM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:
Trunk is the current checkout/branch:
http://svn.apache.org/repos/asf/tika/trunk
++
Chris
[
https://issues.apache.org/jira/browse/TIKA-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Tikhonov updated TIKA-1422:
Attachment: TIKA-1422.oleg.20141021.patch
Were missing imports of image parsers
.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich.100714.patch
I'm seeing test failures from:
{noformat}
Results :
Failed tests: testMultipart(org.apache.tika.parser.mail.RFC822ParserTest):
(..)
Tests run: 538, Failures: 1, Errors: 0, Skipped: 1
{noformat}
CentOS6 VM
Please take a try with newest patch.
Cheers,
Oleg
On Tue, Oct 21, 2014 at 9:08 AM, Oleg Tikhonov olegtikho...@gmail.com
wrote:
Taken. Thanks. in progress ...
On Tue, Oct 21, 2014 at 8:54 AM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:
Trunk is the current
Thanks Oleg, will try tomorrow for me Los angeles time!
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519,
Sorry!!!
On Tue, Oct 21, 2014 at 9:37 AM, Mattmann, Chris A (3980)
chris.a.mattm...@jpl.nasa.gov wrote:
Thanks Oleg, will try tomorrow for me Los angeles time!
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and
[
https://issues.apache.org/jira/browse/TIKA-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178036#comment-14178036
]
Lewis John McGibbney commented on TIKA-1423:
Hi [~vinegh] how is this coming
Hi Chris,
On Mon, Oct 20, 2014 at 11:37 PM, dev-digest-h...@tika.apache.org wrote:
We do need to make a 1.7 release. I¹d like to get TIKA-1422 fully
working on Windows first.
Any one of the other devs having things we should get into 1.7?
I would very much like to see
Thanks Lewis!
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email:
[
https://issues.apache.org/jira/browse/TIKA-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney reassigned TIKA-1423:
--
Assignee: Lewis John McGibbney
Build a parser to extract data from GRIB
[
https://issues.apache.org/jira/browse/TIKA-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178052#comment-14178052
]
Vineet Ghatge commented on TIKA-1423:
-
Hey [~lewismc] I am working on it, I will post
: parser
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Fix For: 1.7
Attachments: TIKA-1422.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich
The Apache Jenkins build system has built tika-trunk-jdk1.7 (build #273)
Status: Failure
Check console output at https://builds.apache.org/job/tika-trunk-jdk1.7/273/ to
view the results.
Issue Type: Bug
Components: parser
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Fix For: 1.7
Attachments: TIKA-1422.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich
.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich.100714.patch
I'm seeing test failures from:
{noformat}
Results :
Failed tests: testMultipart(org.apache.tika.parser.mail.RFC822ParserTest
.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich.100714.patch
I'm seeing test failures from:
{noformat}
Results :
Failed tests: testMultipart(org.apache.tika.parser.mail.RFC822ParserTest
.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich.100714.patch
I'm seeing test failures from:
{noformat}
Results :
Failed tests: testMultipart(org.apache.tika.parser.mail.RFC822ParserTest
Abhishek created TIKA-1452:
--
Summary: parser.parse() throws exception after which the procesed
file is not getting renamed/moved/deleted
Key: TIKA-1452
URL: https://issues.apache.org/jira/browse/TIKA-1452
[
https://issues.apache.org/jira/browse/TIKA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178360#comment-14178360
]
Hudson commented on TIKA-1311:
--
SUCCESS: Integrated in tika-trunk-jdk1.7 #275 (See
[
https://issues.apache.org/jira/browse/TIKA-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178361#comment-14178361
]
Andrew Jackson commented on TIKA-1302:
--
Okay, so the c.300,000 exceptions are here:
[
https://issues.apache.org/jira/browse/TIKA-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178362#comment-14178362
]
Nick Burch commented on TIKA-1452:
--
Can you provide a junit test case that shows how to
[
https://issues.apache.org/jira/browse/TIKA-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178361#comment-14178361
]
Andrew Jackson edited comment on TIKA-1302 at 10/21/14 12:59 PM:
Hi Hong-Thai,
These commits look strange to me - it looks like it subtracts the
whole files (and the unit test removed the test file, renamed it,
and then added what largely looks like the same file, back?)
Any idea what¹s up?
Cheers,
Chris
Thanks Chris. Any ideas when that is likely to happen?
I'm trying to determine whether I can wait for a 1.7 release. If not, I
think my only option to avoid the uncontrolled build up of tmp files (when
processing .7z archives) would be to go back to 1.5.
Regards,
Aeham
I am passing a file as input stream to parser.parse() method while using
apache tika library to convert file to text.The method throws an exception
(displayed below) but the input stream is closed in the finally block
successfully. Then while renaming the file, the File.renameTo method from
Hi Chris,
Yes, I made a mistake on this commit by missing a renaming file and broke
build, the next commit corrected:
Revision: 161
Author: thaichat04
Date: mardi 21 octobre 2014 11:47:54
Message:
TIKA-1422 - Fixing build minor refactory of naming test class
Modified :
No worries Hong-Thai! Will update and test, thanks!
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop:
-1422.Mattmann.100114.patch.txt,
TIKA-1422.Mattmann.100414.patch.txt, TIKA-1422.oleg.20141021.patch,
TIKA-1422.palsulich.100414.patch, TIKA-1422.palsulich.100714.patch
I'm seeing test failures from:
{noformat}
Results :
Failed tests: testMultipart
[
https://issues.apache.org/jira/browse/TIKA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178889#comment-14178889
]
Bin Hawking commented on TIKA-1446:
---
The above attached is my fix, which is the old or
[
https://issues.apache.org/jira/browse/TIKA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Hawking updated TIKA-1446:
--
Attachment: chm.zip
CHM parser : wrong decompression of aligned blocks
[
https://issues.apache.org/jira/browse/TIKA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Hawking updated TIKA-1446:
--
Attachment: (was: chm.zip)
CHM parser : wrong decompression of aligned blocks
All,
I have Intellij set to order imports by javax, java, then other. I think
this is the most common pattern in Tika. Is it ok if I make these
(meaningless/formatting) changes when I commit other changes?
Thank you.
Best,
Tim
Rob Tulloh created TIKA-1453:
Summary: fails to parse RFC3464 documents
Key: TIKA-1453
URL: https://issues.apache.org/jira/browse/TIKA-1453
Project: Tika
Issue Type: Bug
Affects Versions:
On Tue, 21 Oct 2014, Allison, Timothy B. wrote:
I have Intellij set to order imports by javax, java, then other. I
think this is the most common pattern in Tika. Is it ok if I make these
(meaningless/formatting) changes when I commit other changes?
The only downside of this is that the top
[
https://issues.apache.org/jira/browse/TIKA-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179422#comment-14179422
]
Hudson commented on TIKA-1451:
--
SUCCESS: Integrated in tika-trunk-jdk1.7 #276 (See
[
https://issues.apache.org/jira/browse/TIKA-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179441#comment-14179441
]
Hudson commented on TIKA-1451:
--
SUCCESS: Integrated in tika-trunk-jdk1.6 #255 (See
36 matches
Mail list logo
