Packaging and Managing Dependencies

Question

Hi, using Eclipse IDE i have two projects they both use each other's packages ... I get an eclipse error ... "a cycle was detected in a build path of a project eclipse" ... I can easily change this toa warning in eclipse, wondering if this can give run time problems
Thanks

Answer 1

jsunsnx wrote:
interface or abstract classes? Interface or abstract or even just base class is really a matter for design. Any will work.
i wold think the needed class can be made an abstract class in a third project then every class which needs it creates a local child class.. Say i have project A and Project B... Project A needs class bb from B and project B needs class aa from A, how do i implements this using interfaces?Needs it? If you have say 50 classes in one package and 50 in another and all are circular then I can almost guarantee that you have a design problem.
Conversely if you have the following.
1. package A, class X depends on class Y and Z
2. package B, class Y depends on class A, and class Z (no dependency)
Then create package C, with interface Iy and Iz. A uses Iy and Iz. Y implements Iy, Z implements Iz. Y still depends on A.