You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Dan Pritts (JIRA)" <ji...@apache.org> on 2018/03/19 19:24:00 UTC
[jira] [Commented] (JENA-1239) fuseki should not autocreate a
config.ttl file if a configuration file is specified on the command line
[ https://issues.apache.org/jira/browse/JENA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405310#comment-16405310 ]
Dan Pritts commented on JENA-1239:
----------------------------------
Just installed 3.6.0 and this behavior is still present.
> fuseki should not autocreate a config.ttl file if a configuration file is specified on the command line
> -------------------------------------------------------------------------------------------------------
>
> Key: JENA-1239
> URL: https://issues.apache.org/jira/browse/JENA-1239
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Environment: RHEL6, openjdk 1.8.0_101
> Reporter: Dan Pritts
> Priority: Minor
>
> I use the command line to specify a configuration file when I start fuseki. My config is not in $FUSEKI_BASE/config.ttl
> Even so, fuseki autocreates a config.ttl in $FUSEKI_BASE if one does not already exist.
> This could easily be confusing to the next person who comes along (heck, it confused me when rolled back around to fuseki today after being away from it for a few weeks). So, I propose that you add a check (do I have a config file?) before you create the default config.ttl.
> thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)