[
https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143936#comment-13143936
]
Paolo Castagna commented on JENA-36:
------------------------------------
It would be good a shared commong (best) practice for logging and these sort of
things... too much diversity leads to chaos or uglines (and a lot of waste of
time when things do not work as you would expect).
I am about to commit a little bit more ugliness (which eliminates log messages
at ERROR and WARN level when we run the tests, since I agree with the principle
of no spurious warnings/errors when the test suite run). However, I am unclear
on what's the shared practice in relation to testing and logging. Clarify this
would help to do the right thing in future.
> 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
