[
https://issues.apache.org/jira/browse/JENA-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474243#comment-13474243
]
Stephen Allen commented on JENA-334:
------------------------------------
I wrote the script, but I'm not really a bash expert. The problem is that I
couldn't find a recommended way of discovering which directory the script was
executed in. I believe this is partly by design in bash, as scripts may not
actually exist on the filesystem anywhere.
In the meantime, you can work around this issue by setting FUSEKI_HOME
environment variable to the correct path. A patch would be welcome if you know
how to solve this issue.
> Fuseki start script fails when invoked with full pathname
> ---------------------------------------------------------
>
> Key: JENA-334
> URL: https://issues.apache.org/jira/browse/JENA-334
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 0.2.4
> Environment: Cygwin (on Windows 7)
> Reporter: Daniel B.
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Trying to run the main Fuseki start/stop script using a full pathname fails,
> reporting a mangled
> inferred value for the location of the Fuseki installation:
> ~
> $ /cygdrive/c/tools/jena-fuseki-0.2.4/fuseki start 2>&1
> /home/565069//cygdrive/c/tools/jena-fuseki-0.2.4 does not exist
> ~
> $
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
