You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by "Paolo Castagna (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/04 13:55:00 UTC

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

     [ https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paolo Castagna resolved JENA-36.
--------------------------------

    Resolution: Fixed

I'll wait someone else thumb up before definitely closing this one.
                
> 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
>            Assignee: Paolo Castagna
>            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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira