It should be possible to keep drools-verifier in the drools repo. Doing some changes to support this right now.
Toni On Feb 6, 2011, at 11:17 AM, Geoffrey De Smet wrote: > After the split-up drools-verifier is suppose to go into the drools repo > and ide-common is suppose to go into the guvnor repo. > > So drools-verifier can not depend on ide-common. > Is that an option, Toni? > > With kind regards, > Geoffrey De Smet > > Op 04-02-11 23:20, Esteban Aliverti schreef: >> @Geoffrey I started working on this issue. Here is the associated jira >> issue https://issues.jboss.org/browse/GUVNOR-1186 >> <https://issues.jboss.org/browse/GUVNOR-1186>The problem is that >> drools-factconstraints depended on drools-verifier and drools-verifier >> depends on drools-ide-common. So, if I move drools-factconstraints into >> drools-ide-common, I will get a cyclic dependency error (because >> drools-ide-commons will depend on drools-verifier and drools-verifier >> depends on drools-ide-common). >> One solution (and maybe the easiest one) could be to move >> drools-factconstraints into drools-verifier. What do you think about >> this Toni? >> >> Best Regards, >> >> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >> >> Esteban Aliverti >> - Developer @ http://www.plugtree.com <http://www.plugtree.com> >> - Blog @ http://ilesteban.wordpress.com >> >> >> >> _______________________________________________ >> 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 _______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
