[
https://issues.apache.org/jira/browse/TIKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting reopened TIKA-593:
--------------------------------
Reopening until we figure out what to do with the references to the
dev.java.net repositories.
Earlier we had problems with such references to non-standard Maven repositories
and I
wouldn't like to have this issue block another release.
In revision 1079922 I removed the tika-server component from the default build,
which
should allow us to release Tika even with the dev.java.net dependencies in
place (we just
can't deploy tika-server to Maven central then).
There were also some test failures due apparently to some dependency version
mismatch.
See
https://builds.apache.org/hudson/job/Tika-trunk/483/org.apache.tika$tika-server/
for details.
> Tika network server
> -------------------
>
> Key: TIKA-593
> URL: https://issues.apache.org/jira/browse/TIKA-593
> Project: Tika
> Issue Type: New Feature
> Components: general
> Reporter: Jukka Zitting
> Assignee: Maxim Valyanskiy
> Fix For: 1.0
>
>
> It would be cool to be able to run Tika as a network service that accepts a
> binary document as input and produces the extracted content (as XHTML, text,
> or just metadata) as output. A bit like TIKA-169, but without the dependency
> to a servlet container.
> I'd like to be able to set up and run such a server like this:
> $ java -jar tika-app.jar --port 1234
> We should also add a NetworkParser class that acts as a local client for such
> a service. This way a lightweight client could use the full set of Tika
> parsing functionality even with just the tika-core jar within its classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
