On 29/10/11 16:49, Paolo Castagna wrote:
Hi Andy
Just an hypothesis to explain these problems.
The machines used by Jenkins have a Maven repository used to cache
artifacts
including pom.xml files. Maybe, for some reason, one or more pom.xml
files in
the Maven cache on the machines used by Jenkins have not been updated.
Feel free to ignore Jenkins and just make all the changes you want to make,
I'll then look at what's going on with Jenkins and fix the problems.
Don't waste time with it, if you don't want to.
Having two pom.xml files double the amount of testing, having some projects
using pom.xml (old) and pom2.xml (new) and other use pom.xml (new) and
pom1.xml (old), just increase the probability of making mistakes.
Paolo
Unjamming Jena_IRI seems to have fixed the development/install builds
(but I don't know why). We'll see if the overnight snapshot builds get
built.
Andy
