project A depends on project B but in one file in project B I need to call into A. Is there a way to do this? If so how? I thought about an interface and abstract class but I can't figure this out. I want to avoid circular dependencies.
A third project might be just the answer, or you might be able to change things around with an interface. Here's an intro to Dependency Inversion that sometimes does the trick. The first slide is a picture of Robert Martin's "Agile Software Development" which is the place to learn dependency management, highly recommended.
BTW: Kudos for recognizing the problem! Some folks near me at work use a build procedure that deletes all compiled classes and starts from source code. They have two jars that depend on each other, and they cannot build either one first. [ December 06, 2007: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi