Cool, I imagine that this project will be used to define a new API for all the modules right? Is this the project that we should use for some of the experimental APIs? For a while I was pushing some changes in the human tasks module interface, should I include those APIs here?
Cheers - CTO @ http://www.plugtree.com - MyJourney @ http://salaboy.wordpress.com - Co-Founder @ http://www.jbug.com.ar - Mauricio "Salaboy" Salatino - On 12/12/2011, at 11:08, Geoffrey De Smet <[email protected]> wrote: > Hi guys, > > At Mark's and Kris's request, I've created a new module > knowledge-internal-api in droolsjbpm-knowledge. > This module will - in time - contain all the internal API between > drools, jBPM and guvnor. > > Advantages: > > 1) jBPM would no longer need to depend on drools-core. > > 2) It's clear that if you break backwards compatibility of the API in > that module, that drools version X won't work with jbpm version X + 1 > (and vica versa). > Or put differently, if you change something in drools-core, you're safe > (now you are not). > > -- > With kind regards, > Geoffrey De Smet > > > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev _______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
