You should program against interfaces and then you can create a module containing the interfaces and one containing the classes. The dependencies will be from a class module to several source modules.
On Jan 24, 2008 5:02 PM, Guillaume Lederrey <[EMAIL PROTECTED]> wrote: > Usually, if you have circular dependencies only at the module level, > you either have classes packaged in the wrong module or you need to > create one more module. If you have class level circular dependency > (class A depends on class B which depends on class C which depends on > class A), then you'll have to do some heavy refactoring ... > > It's hard to give you a generic answer without knowing exactly why you > have circular dep, and what's their meaning ... > > Good luck ! I'm in the same hell as you for the moment ... > > On 24/01/2008, Rex Huang <[EMAIL PROTECTED]> wrote: > > I see, but some times circle dependence is not easy to cut. > > so we had to find out how to solve this problem. > > Is there any ideas to do it? > > > > Rex > > > > On Jan 24, 2008 3:48 PM, Rémy Sanlaville <[EMAIL PROTECTED]> > wrote: > > > > > Hi, > > > > > > Cyclic dependence is not allowed with maven (it's a good practice). > > > You have to cut your cyclic dependence. > > > > > > Rémy > > > > > > > > -- > Jabber : [EMAIL PROTECTED] > Skype : Guillaume.Lederrey > Projects : > * http://rwanda.wordpress.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
