I did some investigation over the weekend and think I found the problem. I took a couple of steps to try and resolve it.
1) I create a Jenkins build for Jena2 2) I used that build to debug the issue with the tests which did not occur on my home system. 3) I managed to find what I think is the problem. I have update the junit-contracts to 0.1.4 and have kicked off the jena2 build. If the jena2 build succeeds then it should be safe to move jena master to 0.1.4 as well and that should resolve the build problem. It is late here and I am heading to bed, but I will check tomorrow when I get home and will perform the necessary updates to jena master if jena 2 succeeded. Claude On Wed, Jun 17, 2015 at 8:01 PM, Claude Warren <cla...@xenei.com> wrote: > hmmm.... Looking at the code.. > > The only "unusual" thing that the contract test does is build a class path > that is then used to find the classes that are under test. > > I noticed in the Linux case it also failed the contract code. The issue > was that it could not find the dependency in any of the repositories. So > the contract test code there did not execute at all. > > I suppose I should put in an info log that will indicate when the plugin > exits. > > I have found that the system could throw a SecurityException if it can't > create the contract-reports sub-directory in the target directory. > > Looking through the code there are several places where RuntimeExceptions > can be thrown. I am not certain what the Maven Mojo does in that case. > Thinking about it now, I can see that the RuntimeException should probably > be caught and thrown as a MojoExecutionException to keep it from > interrupting the flow of the build. > > > > > On Wed, Jun 17, 2015 at 11:19 AM, Andy Seaborne <a...@apache.org> wrote: > >> Correlation is not causality ... but! >> >> Claude, >> >> The Windows job stopped working last time around the time the version of >> the contract code was updated. >> >> Last time, I wiped the workspace out which seemed to get it working again >> - I don't know what's going on why. The maven output does not show any >> problems - but jena-core is marked "fail". >> >> Does the contract-test-maven-plugin do anything funky? >> >> I've wiped the workspace but it didn't recover this time. >> >> And as to why Windows not Ubuntu, ... simply no idea ... >> >> Lost in maven ... >> >> Andy >> >> On 17/06/15 10:23, Apache Jenkins Server wrote: >> >>> See < >>> https://builds.apache.org/job/Jena_Development_Test_Windows/org.apache.jena$jena-core/578/changes >>> > >>> >>> Changes: >>> >>> [andy] Put back contract plugin (Windows build testing) >>> >>> [claude] converted junit-contracts to version 0.1.3 >>> >>> >> >> [INFO] --- contract-test-maven-plugin:0.1.2:contract-test (default) @ >>> jena-core --- >>> [INFO] Processing package: org.apache.jena.assembler >>> [INFO] Processing package: org.apache.jena.datatypes >>> [INFO] Processing package: org.apache.jena.enhanced >>> [INFO] Processing package: org.apache.jena.graph >>> [INFO] Processing package: org.apache.jena.mem >>> [INFO] Processing package: org.apache.jena.n3 >>> [INFO] Processing package: org.apache.jena.ontology >>> [INFO] Processing package: org.apache.jena.rdf >>> [INFO] Processing package: org.apache.jena.rdfxml >>> [INFO] Processing package: org.apache.jena.reasoner >>> [INFO] Processing package: org.apache.jena.shared >>> [INFO] Processing package: org.apache.jena.util >>> [INFO] Processing package: org.apache.jena.vocabulary >>> [INFO] Skip filter: Not( Wildcard( Sensitive, *.test.* ) ) >>> [JENKINS] Archiving disabled >>> >>> >> > > > -- > I like: Like Like - The likeliest place on the web > <http://like-like.xenei.com> > LinkedIn: http://www.linkedin.com/in/claudewarren > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
