On 19/08/2011 20:44, Wolfgang Laun wrote:
On 19 August 2011 18:07, Mark Proctor <mproctor@codehaus.org> wrote:

Mike just won't explore bugs, without unit tests. Once a unit test is in place he's responsive in fixing it. Which is fair enough.

The point is that for me (and presumably most other Drools users) the step from a DRL construct towards an MVEL unit test isn't a simple one.
-W

We can't write all the software ourselves, we have to re-use OSS libraries and be a part of those communities, and the baggage that comes with them.

We've hired Mario full time, who is now responsible for this area. So that should atleast help in some aspect, as we can be more pro-active in ownership of MVEL issues.

Mark

The problem seems caused by MVEL not properly managing methods accepting a varargs.
I created a failing test and sent a pull request including it: https://github.com/mvel/mvel/pull/11

As Mark wrote, in future I will try to help Mike in testing and possibly fixing those MVEL issues.

Mario