[
https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-1511.
-------------------------------
Resolution: Fixed
r1659449
For now, I chose to set xerial's sqlite-jdbc to "provided" in the pom for two
reasons:
* [~grossws] pointed out that there will be some issues for users running
native libs in a web server unless they carefully configure/arrange their jars.
* As of 3.8.7, sqlite-jdbc is not cleaning up its copying of jars to the temp
folder. Each time Tika is run and parses a Sqlite file, another jar is added
to the user's temp folder.
I don't feel strongly about the choice to set this as "provided". If we'd
rather bundle the jar with tika-app and tika-server, let me know.
> 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
>
> Attachments: TIKA-1511v1.patch, TIKA-1511v2.patch, TIKA-1511v3.patch,
> testSQLLite3b.db, testSQLLite3b.db
>
>
> 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)
