On 14/10/18 13:56, Andy Seaborne wrote:
On 14/10/18 13:47, Claude Warren wrote:
At work we found that creating a build suite that did an install into a
separate local repository solved some pollution problems.
Or quicker : "rm -rf <repo>/org/apache/jena/*" :-)
Or "find <repo>/org/apache/jena/* -name \*SNAPSHOT | xargs rm -rf"
But that's not the issue here.
jena-core code has the wrong import. My bad.
There'll be artifacts when the deploy job completes. It's already
passed TDB2.
Artifacts deployed (the build failed because jena-text-es was making no
progress).
Run locally and deployed the full set of artifacts.
Andy
On Sun, Oct 14, 2018 at 1:25 PM Andy Seaborne <[email protected]> wrote:
Why will that help?
Have you tried deleting the workspace manually first? I don't see a
successful job that has done that.
There is a code bug due to a moved class. I'll fix it.
Andy
On 14/10/18 13:02, Claude Warren wrote:
OK, so the jena development test has not completed for the last 5
builds.
I started the build by hand when it failed and it failed with a
different
error. This is rather disconcerting.
I can't seem to build the entire package on my system.
Perhaps we need a build that deletes the workspace and uses it's own
local
repository to ensure that the entire system can be built. I will
endeavour
to create that jenkins job.
Claude
