Interesting I had no idea something already existed (in some form). While his supports more source type compilations than mine does currently (csv, xls, etc), his requires a bit more configuration than mine does. His requires that you specify which files belong to which compiled unit which can lead to a really noisy pom if you have a very large number of packages and/or source files. This also allows a little bit finer grained control over what source files belong in which compiled unit over my implementation. Mine on the other hand, traverses the identified source directory and programmatically groups together source files with identical package names. This requires less configuration in the pom, however you have less control over how/what goes into a serialized package. It assumes if you have multiple rules identified with identical package names, you want these packaged together. I certainly see merits in both implementations. I guess if this never made it anywhere there's not a lot of need for a pre-compilation mojo. Eric On Fri, 2008-03-07 at 14:42 -0300, Fernando Meyer wrote:Hi Eric, Someone already made a contrib of a maven plugin, I think I did some review on that code but it never went to mainstream. could you please compare your code to the attachment? http://jira.jboss.org/jira/browse/JBRULES-1273 On Fri, Mar 7, 2008 at 1:22 PM, Eric Miles <eric.miles@kronos.com> wrote: I have not performed any tests on this, but I'm sure the Drools guys could comment on it as they provide serialized vs non-serialized support in the framework. I would have to think it would decrease initialization time as you're only de-serializing objects vs compiling a rule set. Of course, your build time will increase :) Our main goal was to limit the number (and size) of the jars we had to include in our application as we already had a very large distributable for our application. Some features of the compilation mojo: - Precompiles drls, ruleflow, and dsl into their individual packages - Supports single package being spread across multiple DRL and rule flow files using same package name. - Supports DSL through a specific naming convention (some work could be done here to be a little more flexible) - Supports compression to decrease serialized package file sizes (Currently gzip, could tweak to support other compressions) - Serializes via XStream (could be tweaked to support different serialization mechanisms) Eric On Fri, 2008-03-07 at 16:57 +0100, Geoffrey De Smet wrote: > Sounds interesting. > Does it noticeably decrease RuleBase initialization time at runtime? > > With kind regards, > Geoffrey De Smet > > > Eric Miles wrote: > > Is there a Maven Drools compilation mojo, provided either by the Drools > > team or some open source project? If not, I have one that I'd be > > willing to submit. I think it's pretty slick and would only require a > > few tweaks to truly make it useful (hard coded to currently use XStream > > serialization). > > _______________________________________________ > > rules-users mailing list > > rules-users@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/rules-users > > > > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users -- Fernando Meyer http://fmeyer.org JBoss Rules Core Developer fernando@fmeyer.org _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users