<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 19/08/2011 20:44, Wolfgang Laun wrote:
<blockquote
cite="mid:CANaj1LdPNSLx3k3LGYq7nqc-hLhqc7jm=VFK0bUgB0RzJAmqhQ@mail.gmail.com"
type="cite">On 19 August 2011 18:07, Mark Proctor <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:mproctor@codehaus.org">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 class="h5"><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>
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>
<br>
Mark<br>
<blockquote
cite="mid:CANaj1LdPNSLx3k3LGYq7nqc-hLhqc7jm=VFK0bUgB0RzJAmqhQ@mail.gmail.com"
type="cite"><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>