[
https://issues.apache.org/jira/browse/TIKA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583183#action_12583183 ]
Jukka Zitting commented on TIKA-135:
------------------------------------
The command files expect that you run them as bin/tika or bin\tika.bat, i.e. that the lib directory is a directly below the current working directory. To properly solve this issue we should add some code that determines the bin directory path from $0 and uses that to generate the lib path.
The more I think about this, the more it seems like a good idea to reopen TIKA-115 and instead implement it simply as a runnable tika.jar that bundles all the required dependencies.
PS. See
http://markmail.org/message/aajf2ttv573dqdhe for Karl's proposed patch.
> The command line files (tika.bat, tika.sh) are not usable
> ---------------------------------------------------------
>
> Key: TIKA-135
> URL:
https://issues.apache.org/jira/browse/TIKA-135> Project: Tika
> Issue Type: Bug
> Affects Versions: 0.2-incubating
> Environment: Windows XP; Java 1.5
> Reporter: Karl Heinz Marbaise
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> The bat/sh file do not include the correct path to the jar's nor to the classpath where all other files can be found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
