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

["Andy Seaborne (Reopened) (JIRA)" <ji...@apache.org>]

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

Andy Seaborne reopened JENA-36:
-------------------------------


There is a small problem with the build because of log4j.properties.

There is no supplied log4j.properties when doing the maven building/testing (e.g. ARQ) - this leads to warnings.

e.g. ARQ:
Running org.openjena.atlas.io.TS_IO
log4j:WARN No appenders could be found for logger (org.openjena.atlas.io.BufferingWriter).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Suggestion: put a log4j.properties into jena-test.jar.

                
> 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