I believe the idea was to find a common place for small utility classes, for UF, Drools and jBPM. Things like StringUtils, IoUtils, ClassUtils etc. All projects need those, and it avoids duplication.
Mark On 2 Apr 2013, at 15:09, Michael Anstis <michael.ans...@gmail.com> wrote: > 1) UberFire and any module dependent on that (Guvnor NG, jBPM Console NG, > jBPM Designer NG) use kie-commons. > > AFAIK kie-comons was a separate module as the VFS (it's principle component) > was meant to be used elsewhere including Drools. > > 2) I'd think merging it would be a bad idea as it isn't meant to be part of > Drools, but used by it. > > The same goes for UberFire.. that whilst under droolsjbpm isn't really part > of it. > > Alexandre could probably comment further (whenever he's back?!?). > > > > On 2 April 2013 15:00, Geoffrey De Smet <ge0ffrey.s...@gmail.com> wrote: > The git repo kie-commons is currently build before drools. > Does that mean that drools uses code from kie-commons? > 1) Which modules are depending on kie-commons's modules? > > kie-commons's name is confusing to several people, including myself. > > > The git repo kie-commons does not contain the modules kie-api or kie-internal. > The modules kie-api or kie-internal are in the git repo droolsjbpm-knowledge. > 2) Would it make sense if we merge the git repo's droolsjbpm-knowledge and > kie-commons? > > > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev > > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
