<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 19/08/2011 17:07, Mark Proctor wrote:
<blockquote cite="mid:4E4E8A2C.1010208@codehaus.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 19/08/2011 16:45, Wolfgang Laun wrote:
<blockquote
cite="mid:CANaj1LcQSYnpqE80nPq-rOtNsTN6qDW-ZtwMFbu80iGxYh99sw@mail.gmail.com"
type="cite">I'll not create any JIRAs for problems that come and
go with the presence and absence of dialect "mvel".<br>
<br>
After one of those, Mark has urged me to create another JIRA for
MVEL, and this I just won't do. For me, as a <i>Drools </i>user,
this project <i>Drools </i>has adopted MVEL as a vehicle for
primary expression and statement evaluation; since 5.2.0 it
seems that I don't have a choice for some parts of the Drools
language. For me, this means that the full responsibility now
rests with the Drools team - I cannot simply work around by
sticking with 'dialect "java"'.<br>
</blockquote>
</blockquote>
The best way to get MVEL fixed is to submit unit tests. Such as the
examples here:<br>
<a class="moz-txt-link-freetext" href="https://github.com/mvel/mvel/blob/master/src/test/java/org/mvel2/tests/core/CoreConfidenceTests.java">https://github.com/mvel/mvel/blob/master/src/test/java/org/mvel2/tests/core/CoreConfidenceTests.java</a><br>
<br>
Mike isn't religious about jiras, but he will insist on a unit test.
Using a github fork to write the unit test and then submit a pull
request is trivial to do.<br>
<blockquote cite="mid:4E4E8A2C.1010208@codehaus.org" type="cite">
<blockquote
cite="mid:CANaj1LcQSYnpqE80nPq-rOtNsTN6qDW-ZtwMFbu80iGxYh99sw@mail.gmail.com"
type="cite"> <br>
Sorry if this sounds harsh and egocentric, but what I've heard
about MVEL maintainer's non-eagerness for fixing bugs hasn't
inspired me to do otherwise. (Since this is hearsay, I should
add the politically correct statement: "innocent until proven
otherwise".)<br>
</blockquote>
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>
<br>
Mark<br>
<blockquote
cite="mid:CANaj1LcQSYnpqE80nPq-rOtNsTN6qDW-ZtwMFbu80iGxYh99sw@mail.gmail.com"
type="cite"> <br>
Regards<br>
Wolfgang<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" 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>
<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>