[
https://issues.apache.org/jira/browse/JENA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955659#comment-15955659
]
Andy Seaborne commented on JENA-1297:
-------------------------------------
[~ajs6f] -- yes you can if you are setup for Jenkins (IIRC you have ask infra -
maybe a PMC member can do it - it'll be documented under "apache.org/dev" - I
haven't looked fro quiet some time).
Or do a local build and "mvn deploy" -- it'll go to the maven snapshot repo.
ASF Jenkins isn't magic.
I would it but I don't see a commit.
Just merge the PR to master now and I'll kick off a build and we can try it
out. If I miss it, it'll build tonight. At the very worst (unlikely) we can
revert it.
If get too cautious, we'll end up making little progress.
> 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)
