incubator-jena-dev mailing list archives

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


Andy Seaborne commented on JENA-36:

Aren't the ERRORs that happen are ones that are expected (i.e. the test is supposed to generate
an error). i.e they aren't errors as far as the suite is concerned.

An unexpected ERROR is an error and should cause a test failure presumably.

[[ slf4j documentation (and log4j)
          The ERROR level designates error events that might still allow the application to
continue running.

> 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