Hi Rob,
I've got the full build (deploy) building by using java7. It's not that
it is always broken with Java6. The test build is still Java 6 and that
usually works; it might be load-on-build-server sensitive. It builds
fully on my local machine in either set up. (I have added connection
caching to Fuseki test as well.)
> What are the build exceptions in JDBC / JenaStatement?
There's log at:
https://builds.apache.org/job/Jena_Development_Deploy/437/console
from about 25% to 50% of the scroll bar.
I have a version locally that is clean. I found that the tests reset
Log4j and then remove all the appenders which causes the warning about
log4j:WARN No appenders could be found for logger
(org.apache.jena.riot.stream.JenaIOEnvironment).
etc
but it also stops configuring the logging from src/test/resources as
this is ignored. That confused me for a while :-)
I'd guess this was just debugging setup? Also, there is logging to a
file, I switched that off as well.
jena-jdbc-log4j.properties, which is src/main so goes in the final jar
but as far as I can see, it's only used in TestMemDriverWithLogging.
A question:
The POM says aspectj plugin is for debugging purposes.
(and how do you get it working with Eclipse? When I add a maven nature
I get errors and Eclipse refuses to compile the JDBC projects).
Andy
