See <https://builds.apache.org/job/Jena_Development_Test_Windows/199/changes>
Changes: [andy] Fix javadoc warnings [andy] Put back aspectj plugin [andy] [andy] Stray file [andy] Supress expected warnings in the tests. [andy] Configure surefire to pick up log4j.properties from src/test/resources [andy] Add Apache header [andy] log4j.properties for testing [andy] Put logging control in src/test/resources\nSupress expected log messages (and exception dumps) from the build. [andy] Add Apache License header [andy] Remove @author's [andy] Update parent apache POM version [andy] Control logging in testing from src/test/resources\nAvoid putting a log4j.properties in the main jar [andy] Tweak DEPENDENCIES [andy] Switch to TriG that follows the draft RDF 1.1 syntax. [andy] Add testing log4.properties. ------------------------------------------ Started by an SCM change Building remotely on windows1 in workspace <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/> Cleaning up <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/trunk> Updating http://svn.apache.org/repos/asf/jena/trunk at revision '2013-09-09T11:09:30.617 +0100' D BUILD A jena-security\src\test\resources\log4j.properties U jena-security\pom.xml U pom.xml U jena-arq\src\test\java\org\apache\jena\riot\lang\TestLangTrig.java U jena-arq\src\main\java\org\apache\jena\riot\lang\LangTriG.java U jena-arq\ReleaseNotes.txt U jena-arq\log4j.properties U jena-core\src\main\java\com\hp\hpl\jena\rdf\model\Model.java U jena-core\src\main\java\com\hp\hpl\jena\reasoner\rulesys\impl\RETEQueue.java U jena-core\src\main\java\com\hp\hpl\jena\reasoner\rulesys\impl\BindingVectorMultiSet.java U jena-parent\pom.xml D jena-spatial\log4j.properties U jena-spatial\DEPENDENCIES U jena-spatial\src\test\resources\log4j.properties U jena-spatial\src\test\java\org\apache\jena\query\spatial\AbstractTestIndexingSpatialData.java U jena-spatial\src\test\java\org\apache\jena\query\spatial\TS_Spatial.java D jena-spatial\src\main\java\log4j.properties U jena-spatial\pom.xml A jena-jdbc\jena-jdbc-driver-bundle\src\test\resources\log4j.properties U jena-jdbc\jena-jdbc-driver-bundle\pom.xml U jena-jdbc\jena-jdbc-driver-tdb\src\test\java\org\apache\jena\jdbc\tdb\metadata\TestTdbConnectionMetadata.java A jena-jdbc\jena-jdbc-driver-tdb\src\test\resources\log4j.properties U jena-jdbc\jena-jdbc-driver-tdb\pom.xml A jena-jdbc\jena-jdbc-driver-remote\src\test\resources\log4j.properties U jena-jdbc\jena-jdbc-driver-remote\pom.xml A jena-jdbc\jena-jdbc-driver-mem\src\test\resources\log4j.properties U jena-jdbc\jena-jdbc-driver-mem\src\test\java\org\apache\jena\jdbc\mem\connections\TestDatasetConnection.java U jena-jdbc\jena-jdbc-driver-mem\pom.xml A jena-jdbc\jena-jdbc-core\src\test\resources\log4j.properties U jena-jdbc\jena-jdbc-core\src\test\java\org\apache\jena\jdbc\TestCompatibility.java U jena-jdbc\jena-jdbc-core\src\test\java\org\apache\jena\jdbc\AbstractJenaDriverTests.java U jena-jdbc\jena-jdbc-core\src\test\java\org\apache\jena\jdbc\results\AbstractResultSetTests.java U jena-jdbc\jena-jdbc-core\src\test\java\org\apache\jena\jdbc\connections\AbstractJenaConnectionTests.java U jena-jdbc\jena-jdbc-core\pom.xml U jena-jdbc\pom.xml At revision 1521022 Parsing POMs ERROR: Failed to parse POMs hudson.util.IOException2: remote file operation failed: <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/trunk> at hudson.remoting.Channel@5dfd6a9b:windows1 at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:882) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:920) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:652) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567) at hudson.model.Run.execute(Run.java:1603) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact org.apache.jena:jena-parent:pom:7-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 27, column 11 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1323) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1058) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2423) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact org.apache.jena:jena-parent:pom:7-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 27, column 11 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1260) ... 12 more
