[
https://issues.apache.org/jira/browse/JENA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584936#comment-15584936
]
Andy Seaborne commented on JENA-1239:
-------------------------------------
Agreed it is confusing and ought to be changed.
I can see 3 choices when a configuration file is given on the command line:
# Not create a default config.ttl if one does not already exist.
# Use the supplied configuration file, so that just running the server, no
command line args, runs it in the same way as before (untested as to whether
that actually works)
# Put in a marker to say "no configuration file - must be on command line" so
that when the server is run again (no command line args), it does not then
create the file.
> 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
(v6.3.4#6332)
