[
https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290096#comment-13290096
]
Andy Seaborne commented on JENA-36:
-----------------------------------
Fixed by
1/ The apache-jena download has a file jena-log4j.properties that the scripts
now all include via -Dlog4j.configuration
2/ If run as "java -cp lib/* ...." a built-in log4j properties is used (in jena
jar or a java string depending on which system; for development, just a file in
jena.jar may not work always).
> log4j.properties can be a surprise
> ----------------------------------
>
> Key: JENA-36
> URL: https://issues.apache.org/jira/browse/JENA-36
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Benson Margulies
> Assignee: Paolo Castagna
> Priority: Minor
> Fix For: Jena 2.7.1
>
>
> 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
