[
https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143986#comment-13143986
]
Andy Seaborne commented on JENA-36:
-----------------------------------
More style than necessity:
Would it be better to call the properties file "jena-test-log4j.properties" --
it's being explicitly set by the code and so we can use a name that is not the
default (the original issue with JIRA)
Turning on /off around the test or the suite is, to me, the best way. (I do
this a lot in ARQ testing for changes to internal global switches).
There is code (in Atlas) to turn logging on and off programmatically for
specific classes, but you have to call the log4j / JUL levels directly.
org.openjena.atlas.logging.Log#enable #disable.
> 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
