[
https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012002#comment-13012002
]
Benson Margulies commented on JENA-36:
--------------------------------------
Two options.
1. Move all commands to their own jar, including log4j.properties.
2. Rename log4j.properties to jena-command-log4.properties, and modify the
command 'main' procedures to use System.setProperty to instruct Jena to use it.
Thus, programs incorporating Jena would not see it.
> log4j.properties can be a surprise
> ----------------------------------
>
> Key: JENA-36
> URL: https://issues.apache.org/jira/browse/JENA-36
> Project: Jena
> Issue Type: Bug
> Reporter: Benson Margulies
> Priority: Minor
>
> The jena jar, and perhaps others, has a log4j.properties on behalf of the
> commands. A little classpath confusion can end up with this at the head of
> the line of an app that is incorporating the jar.
> It would be more better, if you ask me, for the commands to use the -D for
> log4j to ask for a different file name, and leave *that* in the jar.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
