The Apache Jenkins build system has built tika-trunk-jdk1.7 (build #57)
Status: Failure
Check console output at https://builds.apache.org/job/tika-trunk-jdk1.7/57/ to
view the results.
The Apache Jenkins build system has built tika-trunk-jdk1.6 (build #57)
Status: Failure
Check console output at https://builds.apache.org/job/tika-trunk-jdk1.6/57/ to
view the results.
Andrew Skiba created TIKA-1344:
--
Summary: Ability to generate self-contained HTML with images
Key: TIKA-1344
URL: https://issues.apache.org/jira/browse/TIKA-1344
Project: Tika
Issue Type: Improv
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Skiba updated TIKA-1344:
---
Attachment: word.patch
Patch, fixing the issue
> Ability to generate self-contained HTML with images
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037164#comment-14037164
]
Nick Burch commented on TIKA-1344:
--
I think the plan was always that people would have the
Hi Nick
On 18/06/14 17:07, Nick Burch wrote:
On Wed, 18 Jun 2014, Sergey Beryozkin wrote:
The reason we need it is that CXF can not ship all of Tika Parser
dependencies because CXF will only offer a light-weight Tika-aware
handler.
Sounds like you just want to depend on tika-core then, and not
Hi
On 19/06/14 01:58, Ray Gauss wrote:
The point of a tika-parsers-all artifact would be a single dependency that
re-aggregates everything so that downstream projects could work the same way
they do now and not worry about missing dependencies.
Meanwhile people that just want PDF parsing could
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037207#comment-14037207
]
Andrew Skiba commented on TIKA-1344:
As far as I understand, the handler has no access
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037212#comment-14037212
]
Nick Burch commented on TIKA-1344:
--
You won't fetch the Picture directly. Instead, you'll
[
https://issues.apache.org/jira/browse/TIKA-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037219#comment-14037219
]
Dave Meikle commented on TIKA-1343:
---
Hey Chris - I am up for building out on this one. Wi
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037236#comment-14037236
]
Andrew Skiba commented on TIKA-1344:
Can you give an example in existing code for such
[
https://issues.apache.org/jira/browse/TIKA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037243#comment-14037243
]
Nick Burch commented on TIKA-1344:
--
There are some examples on the wiki -
https://wiki.ap
On Jun 19, 2014, at 2:53am, Sergey Beryozkin wrote:
> Hi
> On 19/06/14 01:58, Ray Gauss wrote:
>> The point of a tika-parsers-all artifact would be a single dependency that
>> re-aggregates everything so that downstream projects could work the same way
>> they do now and not worry about missin
Hi Tim, sorry for a delay,
I can see it is expected to process a checked exception, so unless we
have one of the root resources throwing it from one of the methods then
it is not used
Thanks, Sergey
On 19/06/14 02:22, Allison, Timothy B. wrote:
All,
In working on adding the stacktrace fro
Luis created TIKA-1345:
--
Summary: Bad signature in gpg, md5 and sha1 verification
Key: TIKA-1345
URL: https://issues.apache.org/jira/browse/TIKA-1345
Project: Tika
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037601#comment-14037601
]
Nick Burch commented on TIKA-1345:
--
Which mirror did you download the files from?
> Bad s
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037605#comment-14037605
]
Nick Burch commented on TIKA-1345:
--
FWIW, when I check on the master ASF download server (
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037636#comment-14037636
]
Luis commented on TIKA-1345:
I downloaded from https://tika.apache.org/download.html
> Bad sig
No problem at all! Thank you.
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Thursday, June 19, 2014 12:01 PM
To: dev@tika.apache.org
Subject: Re: Is TikaExceptionMapper in tika-server actually used?
Hi Tim, sorry for a delay,
I can see it is expected to
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037673#comment-14037673
]
Nick Burch commented on TIKA-1345:
--
That page will give you a mirror near-ish you, which m
All,
As part of Tika-1302/TIKA-1330, I'm looking into exception handling in
tika-server. Specifically, I'd like to add a TikaServerDaemon that starts Tika
server in a separate process (not thread) and can restart it when necessary.
This is somewhat based on an idea from William Palmer
(http
On Thu, 19 Jun 2014, Ray Gauss wrote:
The point of a tika-parsers-all artifact would be a single dependency
that re-aggregates everything so that downstream projects could work the
same way they do now and not worry about missing dependencies.
What’s the disadvantage for splitting things up (i
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037929#comment-14037929
]
Luis commented on TIKA-1345:
Ok, this was my fault, in part. I right-clicked in the hyper-link
[
https://issues.apache.org/jira/browse/TIKA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Burch resolved TIKA-1345.
--
Resolution: Not a Problem
I'm closing the issue, based on the comments that the real downloaded files ar
On Thu, 19 Jun 2014, Allison, Timothy B. wrote:
I won't make any changes until after 1.6 is released, and the default
behaviors will all remain in place, but I wanted to get feedback from
the community to make sure that I'm on a track that makes sense.
The only precident that springs to mind i
25 matches
Mail list logo