[
https://issues.apache.org/jira/browse/JENA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304394#comment-14304394
]
ASF subversion and git services commented on JENA-877:
------------------------------------------------------
Commit 322696e4553f8587c08de52559bda1d893d9fe45 in jena's branch
refs/heads/master from [~rvesse]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=322696e ]
Avoid log4j warnings in Elephas tests (JENA-877)
Adds a src/test/resources/log4j.properties in the relevant modules
Log output is captured under target/tests.log to avoid cluttering the
Maven 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)
