The Apache Jenkins build system has built tika-trunk-jdk1.7 (build #54)
Status: Failure
Check console output at https://builds.apache.org/job/tika-trunk-jdk1.7/54/ to
view the results.
The Apache Jenkins build system has built tika-trunk-jdk1.6 (build #54)
Status: Still Failing
Check console output at https://builds.apache.org/job/tika-trunk-jdk1.6/54/ to
view the results.
[
https://issues.apache.org/jira/browse/TIKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14035362#comment-14035362
]
Axel Dörfler commented on TIKA-1063:
The patch still applies on branches/1.5 as well as
Though we can exclude some of the dependencies directly in our pom.xml,
that can work too.
We'll experiment a bit with which dependencies are absolutely needed for
tika-parsers and which may be excluded.
Any feedback will be apreciated
Thanks, Sergey
On 17/06/14 21:16, Sergey Beryozkin wrote:
I think for 2.0 we should consider splitting out parsers into their own
projects for a streamlined dependency hierarchy then reassembling them with
something like a tika-parsers-all artifact.
On June 17, 2014 at 5:08:38 PM, Nick Burch (apa...@gagravarr.org) wrote:
On Tue, 17 Jun 2014, Sergey
Hi
On 18/06/14 13:52, Ray Gauss wrote:
I think for 2.0 we should consider splitting out parsers into their own
projects for a streamlined dependency hierarchy then reassembling them with
something like a tika-parsers-all artifact.
something like that will make sense IMHO
On June 17, 2014
Nice Chris.
On Tue, Jun 17, 2014 at 5:59 PM, dev-digest-h...@tika.apache.org wrote:
In the meanwhile I should have a review board patch up soon too for
the JoshuaTranslator.
I'll keep my eyes peeled for this one.
Thanks
Lewis
[
https://issues.apache.org/jira/browse/TIKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14035714#comment-14035714
]
Tyler Palsulich commented on TIKA-994:
--
application/vnd.solent.sdkm+xml is the proper
Hi,
In the current code, the images from Word documents are referenced by
embedded:xxx links in the generated HTML. This causes the browsers
display x icon instead of the image.
The proposed patch encodes the images using Data URI, if there is
-Dtika.parsers.urlimages system property.
On Wed, 18 Jun 2014, Ray Gauss wrote:
I think for 2.0 we should consider splitting out parsers into their own
projects for a streamlined dependency hierarchy then reassembling them
with something like a tika-parsers-all artifact.
We had another thread on that not that long ago, where someone
Hi Nick
On 18/06/14 16:38, Nick Burch wrote:
On Wed, 18 Jun 2014, Ray Gauss wrote:
I think for 2.0 we should consider splitting out parsers into their
own projects for a streamlined dependency hierarchy then reassembling
them with something like a tika-parsers-all artifact.
We had another
On 18/06/14 16:58, Sergey Beryozkin wrote:
Hi Nick
On 18/06/14 16:38, Nick Burch wrote:
On Wed, 18 Jun 2014, Ray Gauss wrote:
I think for 2.0 we should consider splitting out parsers into their
own projects for a streamlined dependency hierarchy then reassembling
them with something like a
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
tika-parsers. That'll give you mime magic
On Wed, 18 Jun 2014, Sergey Beryozkin wrote:
Can we start with adding a section to Tika docs documenting the core
dependencies of the tike-parsers module to make the life a bit easier for
developers who do not expect the specific parser implementations immediately
downloaded ?
Are you not
[
https://issues.apache.org/jira/browse/TIKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14035883#comment-14035883
]
Axel Dörfler commented on TIKA-1063:
Hi Tyler,
if I had known that a little nudge
[
https://issues.apache.org/jira/browse/TIKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14035971#comment-14035971
]
Tyler Palsulich commented on TIKA-1063:
---
Hi,
;) I tried switching it and they still
Hi Nick,
On Jun 18, 2014, at 9:07am, Nick Burch apa...@gagravarr.org 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
Chris A. Mattmann created TIKA-1343:
---
Summary: Create a Tika Translator implementation that uses
JoshuaDecoder
Key: TIKA-1343
URL: https://issues.apache.org/jira/browse/TIKA-1343
Project: Tika
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22761/
---
Review request for tika.
Bugs: tika-1343
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22761/
---
(Updated June 18, 2014, 10:04 p.m.)
Review request for tika.
Bugs: tika-1343
[
https://issues.apache.org/jira/browse/TIKA-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14036503#comment-14036503
]
Chris A. Mattmann commented on TIKA-1343:
-
Review Board up here:
[
https://issues.apache.org/jira/browse/TIKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved TIKA-994.
Resolution: Fixed
Thanks to [~tpalsulich] for the resolution, closing.
Type Detection
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 declare only the
tike-parser-pdf
All,
In working on adding the stacktrace from a parse exception to the server
response, I'm trying to find the most jax-rsly elegant way of handling
exceptions. There seems to be a bit of duplicated code, some with good reason,
for exception handling. Is TikaExceptionMapper actually used
24 matches
Mail list logo
