Dan Pritts commented on JENA-1239:

In (2), do you mean copying the config file from the command line into the 
default location?  That isn't what I'd want - If I'm switching between a 
manually specified file and then leaving the option off, I would expect to get 
some set of built-in defaults when I don't specify.

(3) is pretty good, better than (1).  

Upon further thought, though, I propose (4) - compile in a set of defaults that 
are equivalent to the contents of the config.ttl you'd create, and don't ever 
autocreate a configuration file.  Include the default file in the distribution, 
perhaps named something like "config.ttl.defaults" or with everything commented 
out, but indicating what the defaults are.

> 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

Reply via email to