It appears that these changes have been made. mvn -U brought down some new
snapshots and all my prior NoSuchMethodError problems went away.
Now I am encountering (not surprisingly) other issues.
Specifically, the following rule:
rule "Testing contains"
dialect "mvel"
when
Response( $answerSelections : answerSelections )
AnswerSelection( answer.ID in (2, 3) )
then
System.out.println("Testing contains activated")
end
...produces an error message like this:
[Error: Failed to compile: 1 compilation error(s):
- (1,9) unqualified type in strict mode for: ID]
[Near : {... Unknown ....}]
^
[Line: 1, Column: 0] : [Rule name='Testing contains']
AnswerSelection has a getAnswer() method, and Answer has a getID() method.
This rule passed mere days ago. I seem to recall the notion of
distinguishing between typesafe and non-typesafe constructs is a new 5.2.0
idea; maybe this is the next thing to need to be fixed?
Thanks,
Laird
On Tue, Mar 22, 2011 at 6:15 PM, salaboy [via Drools - Java Rules Engine] <
ml-node+2717564-400506162-10124(a)n3.nabble.com> wrote:
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 <[hidden
email]<http://user/SendEmail.jtp?type=node&node=2717564&i=0&by-user=t>
> 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-t...
>
> 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 <[hidden
email]<http://user/SendEmail.jtp?type=node&node=2717564&i=1&by-user=t>
> > 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...
>> Sent from the Drools - Dev mailing list archive at
Nabble.com.
>> _______________________________________________
>> rules-dev mailing list
>> [hidden
email]<http://user/SendEmail.jtp?type=node&node=2717564&i=2&by-user=t>
>>
>>
https://lists.jboss.org/mailman/listinfo/rules-dev
>>
>
>
> _______________________________________________
> rules-dev mailing list[hidden email]
<
http://user/SendEmail.jtp?type=node&node=2717564&i=3&by-user=...
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> --
> With kind regards,
> Geoffrey De Smet
>
>
> _______________________________________________
> rules-dev mailing list[hidden email]
<
http://user/SendEmail.jtp?type=node&node=2717564&i=4&by-user=...
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> --
> With kind regards,
> Geoffrey De Smet
>
>
> _______________________________________________
> rules-dev mailing list
> [hidden
email]<http://user/SendEmail.jtp?type=node&node=2717564&i=5&by-user=t>
>
>
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 -
_______________________________________________
rules-dev mailing list
[hidden
email]<http://user/SendEmail.jtp?type=node&node=2717564&i=6&by-user=t>
https://lists.jboss.org/mailman/listinfo/rules-dev
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://drools-java-rules-engine.46999.n3.nabble.com/Drools-5-2-0-SNAPSHOT...
To unsubscribe from Drools 5.2.0-SNAPSHOT: NoSuchMethodError, click
here<http://drools-java-rules-engine.46999.n3.nabble.com/template/Naml...;.