Jari also encountered
this problem.
The problem is caused by nexus having recent drools-core
snapshots and old drools-compiler snapshots (as the second
fails).
0) We cannot revert to a previous working timestamp, because
there is no working timestamp since the artifacts have been
renamed (=split-up).
1) As a workaround there's been decided to deploy
test-failing snapshots of drools-compiler,
drools-decisiontables, drools-verifier, ...
Most of the tests work. This situation will give a similar
experience as when we had the monolithic build and there
were test failures in drools-compiler on trunk.
Let's hope hudson is blue soon.
2) The bigger issue is that drools-core should not be
deployed if drools-compiler fails.
Once hudson decently supports maven 3 jobs, I 'll fix that.
Op 13-03-11 14:40, Geoffrey De Smet schreef:
Laird,
We're alive and you're not alone at all :)
We 're all waiting on Edson and Mark to fix this for
us.
Guvnor and droolsjbpm-tools (=eclipse plugin) are also
broken meanwhile.
The root of the problem is that both Mark and Edson
were working on big changes when the clearly announced
split-up had to be executed.
The unfinished problems of those 2 big changes
multiplied against each other and they 've been
working on getting them fixed in the last few weeks.
Because the split-up renamed a lot of artefacts etc,
it's not practical to use guvnor/droolsjbpm-tool on
the latest working snapshots.