[
https://issues.apache.org/jira/browse/JENA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955777#comment-15955777
]
A. Soroka commented on JENA-1297:
---------------------------------
[~zakmck], if the test that seems to be stuck is in Elephas, it's probably one
of the I/O tests there that just runs a really long time and you can get a
build much faster by using {{mvn -Pdev clean package}}. In any event, we are
working on getting you a snapshot build right now, and you have cleverly found
a way to test the fix anyway. I will look at the other scripts you mention and
make sure the problem doesn't arise there.
> Code to set 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
> Assignee: A. Soroka
>
> 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)
