incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-36) can be a surprise
Date Fri, 04 Nov 2011 11:51:00 GMT


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.
> can be a surprise
> ----------------------------------
>                 Key: JENA-36
>                 URL:
>             Project: Jena
>          Issue Type: Bug
>            Reporter: Benson Margulies
>            Assignee: Paolo Castagna
>            Priority: Minor
> The jena jar, and perhaps others, has a 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:!default.jspa
For more information on JIRA, see:


View raw message