You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/04/02 15:37:41 UTC
[jira] [Commented] (JENA-1297) Code to ste JENA_HOME in scripts
doesn't work (links)
[ https://issues.apache.org/jira/browse/JENA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952723#comment-15952723 ]
Andy Seaborne commented on JENA-1297:
-------------------------------------
Could someone with OS X check this out?
On Linux, a symlink for JENA_HOME works for me.
(this might all be because the JENA_HOME is set relative which causes the mentioned effect)
> Code to ste JENA_HOME in scripts doesn't work (links)
> -----------------------------------------------------
>
> Key: JENA-1297
> URL: https://issues.apache.org/jira/browse/JENA-1297
> Project: Apache Jena
> Issue Type: Bug
> Components: Cmd line tools
> Affects Versions: Jena 3.2.0
> Environment: OS X 10.11.6 (15G1217). Java 1.8.0_92
> Reporter: Marco Brandizi
>
> I'm trying the script bin/sparql, to me the code that deals with links when setting JENA_HOME is unnecessary, it ends up setting '.' as the prefix for lib/ ad triggering main class not found (when putting $JENA_HOME/bin in PATH).
> The same script works when I set JENA_HOME with the physical path of Jena, not its symlink (which I don't like, because I prefer to upgrade by symlinking the last version to 'jena' and not having to change anything else).
> I've tried a version of such script where I removed all if [ -L ... ] and it works perfectly well. In my opinion, the existing code (using dirname ... && pwd) is enough to track the folder where the script is.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)