Geoffrey,
After the last few weeks manic performance work, where we broke
everything, we are now just in the process on getting trunk working
again and pushing out a milestone release.
1) (Fixed)
2) See comment in jira
3) Damn didn't mean to commit that eclipse project, it was just
something I was messing around with locally - sorry. (Fixed)
4) Will look into this soon.
Thanks for this, it really helps keep us on our toes and move the
project forward. With regards to the build system, more than happy for
you to start maintaing that for us :) We use the pom's for dependency
management but ant for actual building as I just had too many issues
trying to get maven working the way we wanted. I figured if we are
going to move to maven 100% we need to invest in writing our own
plugins, which I don't have time for now. I actually think our current
ant build, with "usage help instructions" is quite a nice system. If
you are planning to stick around and want commit rights, just ask.
Mark
Geoffrey De Smet wrote:
1) Unused, broken import in:
drools-compiler\src\main\java\org\drools\semantics\java\StaticMethodFunctionResolver.java
import antlr.collections.AST; // unused and breaks compiling because
it no longer exists
2) http://jira.jboss.com/jira/browse/JBRULES-537
3) Drools-compiler depends on Jess.
Since Jess isn't open source, it cannot be distributed,
which means that drools-compiler can't be fully build?
Maybe the benchmarks should be moved to a separate module which isn't
included in the default module set?
4) I've also found a bug on the QueryResults on the 3.0.x branch,
which I 'll verify in the trunk (if I can get it to build ;) and
create a testcase for.
[Apparently doing the same query twice and using A and exist(anotherA
with a greater id) gives problems. In 3.0.4 with logical retractions
it works. But anyway, I 'll create a testcase.]
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
