[rules-dev] Drools 5.2.0-SNAPSHOT: NoSuchMethodError => Drools broken

[Mauricio Salatino]

Geoffrey can you please ping me when this problem is solved?
Or at least when we have new snapshots for compiler and core?
Thanks for the report!


On Tue, Mar 22, 2011 at 6:07 PM, Geoffrey De Smet
<ge0ffrey.spam at gmail.com>wrote:

>  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.
>
> Since recently, drools-core is testing successfully, but drools-compiler
> isn't, so only the former is deployed, so this is also annoying,
> I am investigating that part:
>
> http://stackoverflow.com/questions/5196203/configure-a-hudson-maven-job-to-keep-building-if-there-are-test-failures-but-onl
>
> Op 11-03-11 20:00, Esteban Aliverti schreef:
>
> Drools trunk has been unstable from some weeks now. According to Hudson (
> https://hudson.jboss.org/hudson/view/Drools%20jBPM/) it has been never
> built since the codebase was split up.
> I think hudson should be green soon. But you are not the only one waiting
> for it :)
>
>  Best Regards,
>
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
> Esteban Aliverti
> - Developer @ http://www.plugtree.com
> - Blog @ http://ilesteban.wordpress.com
>
>
> On Fri, Mar 11, 2011 at 2:54 PM, ljnelson <ljnelson at gmail.com> wrote:
>
>> Just checking in to see if anyone is alive on this list; downloaded a new
>> drools-core SNAPSHOT today which did not fix the problem.
>>
>> Best,
>> Laird
>>
>> --
>> View this message in context:
>> http://drools-java-rules-engine.46999.n3.nabble.com/Drools-5-2-0-SNAPSHOT-NoSuchMethodError-tp2660470p2666004.html
>>  Sent from the Drools - Dev mailing list archive at Nabble.com.
>> _______________________________________________
>> rules-dev mailing list
>> rules-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-dev
>>
>
>
> _______________________________________________
> rules-dev mailing listrules-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> --
> With kind regards,
> Geoffrey De Smet
>
>
> _______________________________________________
> rules-dev mailing listrules-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> --
> With kind regards,
> Geoffrey De Smet
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>


-- 
 - CTO @ http://www.plugtree.com
 - MyJourney @ http://salaboy.wordpress.com
 - Co-Founder @ http://www.jbug.com.ar

 - Salatino "Salaboy" Mauricio -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20110322/6d75c342/attachment.html