Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Sun, 30 Oct 2011 11:57:32 +0000 (UTC)
From: "Andy Seaborne (Commented) (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: 
 <508208523.38197.1319975852512.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <226774968.3076.1296583109063.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JENA-36) log4j.properties can be a surprise
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JENA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139603#comment-13139603 ] 

Andy Seaborne commented on JENA-36:
-----------------------------------

The test suite is still generating spurious log messages; I think these go back to the log4j change.  There is some interaction as these ERROR messages are to be expected (the tests are supposed to generate the message).

Maybe running the APR syntax error tests needs the log4j setup programmatically changed to not emit any messages.

ERROR [main] (RDFDefaultErrorHandler.java:42) - http://jcarroll.hpl.hp.com/arp-tests/syntax-errors/error001.rdf(line 10 column 33): {E201} Multiple children of property element
ERROR [main] (RDFDefaultErrorHandler.java:42) - unknown-source: {E201} Multiple children of property element
ERROR [main] (RDFDefaultErrorHandler.java:42) - http://www.w3.org/2000/10/rdf-tests/rdfcore/rdf-containers-syntax-vs-schema/error002.rdf(line 29 column 12): {E204} rdf:li is not allowed as an element tag here.
ERROR [main] (RDFDefaultErrorHandler.java:42) - unknown-source: {E204} rdf:li is not allowed as an element tag here.
ERROR [main] (RDFDefaultErrorHandler.java:42) - http://www.w3.org/2000/10/rdf-tests/rdfcore/rdf-ns-prefix-confusion/test0008.rdf(line 35 column 71): {E206} rdf:aboutEachPrefix has been deprecated.
ERROR [main] (RDFDefaultErrorHandler.java:42) - unknown-source: {E206} rdf:aboutEachPrefix has been deprecated.
ERROR [main] (RDFDefaultErrorHandler.java:42) - http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-nested-bagIDs/test009.rdf(line 25 column 53): {E206} rdf:bagID has been deprecated.
ERROR [main] (RDFDefaultErrorHandler.java:42) - unknown-source: {E206} rdf:bagID has been deprecated.
ERROR [main] (RDFDefaultErrorHandler.java:42) - http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-rdf-names-use/error-006.rdf(line 22 column 18): {E205} rdf:resource is not allowed as an element tag here.
ERROR [main] (RDFDefaultErrorHandler.java:42) - unknown-source: {E205} rdf:resource is not allowed as an element tag here.


> 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