You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2015/02/04 01:40:34 UTC

[jira] [Commented] (JENA-877) Elephas Common API tests need log4j.properties

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

Rob Vesse commented on JENA-877:
--------------------------------

The tests will naturally produce various output that is and should be at WARN level even with an appropriate log4j configuration in place because the tests include exercising functionality that has good reason to print warnings but which don't in of themselves indicate any issue to be worried about

I will add an appropriate log4j configuration that routes the logging output into a file under {{target/}} so that the output is captured if needed but doesn't clutter the build output.

> Elephas Common API tests need log4j.properties
> ----------------------------------------------
>
>                 Key: JENA-877
>                 URL: https://issues.apache.org/jira/browse/JENA-877
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: Jena 2.13.0
>            Reporter: Andy Seaborne
>            Assignee: Rob Vesse
>            Priority: Trivial
>
> {noformat}
> Running org.apache.jena.hadoop.rdf.io.types.RdfTypesTest
> {noformat}
> {noformat}
> Running org.apache.jena.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
> {noformat}
> {noformat}
> Running org.apache.jena.hadoop.rdf.mapreduce.filter.TripleInvertedFilterByNoPredicateMapperTest
> {noformat}
> all give:
> {noformat}
> log4j:WARN No appenders could be found for logger (.....).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> {noformat}
> Can we have a src/test/resources log4j/properties?
> (scanning for WARN after a build to look for problems - helps if there are as few WARN false-positives as possible)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)