[
https://issues.apache.org/jira/browse/JENA-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1734.
---------------------------------
Fix Version/s: Jena 3.13.0
Resolution: Fixed
> Add FUSEKI_BASE extra classes directory
> ---------------------------------------
>
> Key: JENA-1734
> URL: https://issues.apache.org/jira/browse/JENA-1734
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Jena 3.12.0
> Reporter: Claude Warren
> Assignee: Claude Warren
> Priority: Trivial
> Fix For: Jena 3.13.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently the fuseki-server script has comments about how to modify the file
> to add extra classes. This can be rather problematic when working in a
> containerized environment like Docker.
> This proposal is to add $FUSEKI_BASE/extra/* to the classpath for
> fuseki-server so that persistent containers like stain/jena-fuseki have a
> non-instrusive mechanism to add/update extra or 3rd party classes.
> I don't see how to implement this in the windows batch file as it does not
> appear to have environment variables set for similar purposes to the linux
> scripts.
> *Background:*
> When running in docker it is possible to mount the FUSEKI_BASE either to
> local storage or on a docker volume. This makes it easier to update the Jena
> /fusekilibraries without losing the data. However, any edits made to add
> jars to FUSEKI_HOME are lost during the update. Adding the
> $FUSEKI_BASE/extra to the startup script means that 3rd party libraries are
> treated like data and not removed when the Jena/fuseki code is updated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
