<br> Well, we try to keep trunk always working. Although, it is a development version and so we can't really ensure there will be no breaks or eventual bugs during development. <br> <br> []s<br> Edson<br> <br>
<br><div><span class="gmail_quote">2008/2/4, Dirk Bergstrom <<a href="mailto:dirk@juniper.net">dirk@juniper.net</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Edson Tirelli was heard to exclaim, On 02/04/08 04:22:<br>> If you are using trunk, look at the interface EvaluatorDefinition as<br>> your entry point. All you need to do is to create an implementation for<br>> it. This is part of the pluggable evaluators framework I'm working on.<br>
<br>That sounds like the way to go. Do you think trunk (or at least this feature)<br>will be stable enough to use by the end of the month? I'm brave...<br><br>> The only part that is not pluggable yet is the parser, but once you are<br>
> done with your implementation, I can fix the parser for you in a couple<br>> minutes.<br>> Join the IRC and talk to me and I can guide you.<br><br>Thanks. I'll show up later this week, after I get the current round of features<br>
rolled out.<br><br>> If you are using older versions of Drools (not trunk) things will be<br>> a lot more complicated. :(<br><br>I don't like complicated.<br><br>> 2008/2/4, Dirk Bergstrom <<a href="mailto:dirk@juniper.net">dirk@juniper.net</a> <mailto:<a href="mailto:dirk@juniper.net">dirk@juniper.net</a>>>:<br>
><br>> It looks like I'm going to need to implement the "intersects"<br>> operator for a<br>> project I'm working on. As in "Does this collection share at least<br>> one element<br>
> with that collection".<br>><br>> Unfortunately, I'm going to need it in about two weeks. Too bad I<br>> didn't plan<br>> ahead...<br>><br>> So, if anyone can send me some pointers on where in the code I should be<br>
> looking, I'd be very grateful. I don't think it will be<br>> particularly difficult<br>> to write the actual code, but I'm worried that I'll never be able to<br>> figure out<br>
> all the places in the codebase that I have to touch.<br>><br>> A ways back, Edson said that I could use the work on "contains" as a<br>> model; is<br>> there a single subversion commit that lists all the files affected<br>
> by that?<br><br><br>--<br>Dirk Bergstrom <a href="mailto:dirk@juniper.net">dirk@juniper.net</a><br>_____________________________________________<br>Juniper Networks Inc., Computer Geek<br>Tel: 408.745.3182 Fax: 408.745.8905<br>
_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> Office: +55 11 3529-6000<br> Mobile: +55 11 9287-5646<br> JBoss, a division of Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a>