[jira] [Commented] (JENA-36) log4j.properties can be a surprise

["Paolo Castagna (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011966#comment-13011966 ] 

Paolo Castagna commented on JENA-36:
------------------------------------

Hi Benson,
I am not sure I clearly understand what you are proposing.

A log4j.properties file is included in the jena-2.6.4.jar file, I am not sure this is a great idea.
if you have other jars in your classpath which include another log4j.properties file, you do not know which one will be used.
It depends on the order how those jars are added to the classpath.

Are you proposing to remove the log4j.properties file from the jena-2.6.4.jar file and add one to the Jena distribution and use that via explicit -Dlog4j.configuration property?

Or, we could rename the log4j.property file included in the jena-2.6.4.jar and explicitly refers to it via -Dlog4j.configuration property.

Can you please clarify what would you like to do?

> 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