[
https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275217#comment-14275217
]
Tim Allison edited comment on TIKA-1511 at 1/13/15 1:59 PM:
------------------------------------------------------------
Thank you, [~grossws]!
Two questions:
1) On how to exclude the native libs...is it ok to require that people
re-bundle, that is just get rid of the dependency in the pom and build from
scratch? Is there a cleaner method?
2) Would it be better to require users who want SQLLite3 parsing to add xerial
to their classpath? We'll probably need to do this for formats that don't
have Apache friendly drivers (afaik: .mdb, .dbf , others?)
was (Author: talli...@mitre.org):
Thank you, [~grossws]!
Two questions:
1) On how to exclude the native libs...is it ok to require that people
re-bundle, that is just get rid of the dependency in the pom and build from
scratch? Is there a cleaner method?
2) Would it be better to require users who want SQLLite3 parsing to add xerial
to their classpath?
> Create a parser for SQLite3
> ---------------------------
>
> Key: TIKA-1511
> URL: https://issues.apache.org/jira/browse/TIKA-1511
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 1.6
> Reporter: Luis Filipe Nassif
> Fix For: 1.8
>
>
> I think it would be very useful, as sqlite is used as data storage by a wide
> range of applications. Opening the ticket to track it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
