On 09/02/15 22:25, Andy Seaborne wrote:
OK - pull request R #25 integrated - Jena is now using org.ops4j.pax.
There is a small issue - 1078 lines of output for jena-osgi-test (and
that is when it works).
This makes reviewing a build for warnings and unexpected output
impossible in any practical way.
Setting src/test/resources/log4j.properties does not seem to help not
does the format change.
The Jenkins test job reports:
-----------------------------------
SLF4J: Class path contains multiple SLF4J bindings.
logging/pax-logging-api/1.8.1/pax-logging-api-1.8.1.jar
org/slf4j/slf4j-log4j12/1.7.6/slf4j-log4j12-1.7.6.jar
-----------------------------------
which may explain why test/resources/log4j.properties is ignored.
Should slf4j be excluded?
How is the logging configured via the maven plugin (the document is
offline ATM)?
-Dorg.ops4j.pax.logging.DefaultServiceLog.level=WARN from the command
line works but is impractical ... which plugin does it need to be set
on? And how?
I'm out of time today to dive into strange system.
How is maven output done?
Andy
There is an OSGi test failure:
https://builds.apache.org/user/andy/my-views/view/Jena/job/Jena_Development_Test/org.apache.jena$jena-osgi-test/1750/testReport/
which I followed back to:
Caused by:
org.sonatype.aether.resolution.VersionRangeResolutionException: Not
highest version found for org.apache.jena:jena-osgi:jar:(0.0,]
which I don't understand.
Andy
