On Sat, Aug 20, 2011 at 12:36 AM, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000"><div><div></div><div class="h5">
On 19/08/2011 20:44, Wolfgang Laun wrote:
<blockquote type="cite">On 19 August 2011 18:07, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org" target="_blank">mproctor@codehaus.org</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div><br>
</div>
</div>
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.<br>
</div>
</blockquote>
<div><br>
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.<br>
-W <br>
</div>
</div>
</blockquote></div></div>
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.<br>
<br>
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.<br><font color="#888888">
<br>
Mark</font><br></div></blockquote><div><br>The problem seems caused by MVEL not properly managing methods accepting a varargs.<br>I created a failing test and sent a pull request including it: <a href="https://github.com/mvel/mvel/pull/11">https://github.com/mvel/mvel/pull/11</a><br>
<br>As Mark wrote, in future I will try to help Mike in testing and possibly fixing those MVEL issues.<br><br>Mario<br> </div></div>