Hi, this sounds like a not so good design. You never want two differened packages to have that kind of circular dependency.
What propably need to do to solve it: - Extract the common used interface into a seperate package, which is then used by the existing packages. Regards, Tjeerd On 8/13/07, bhatia <[EMAIL PROTECTED]> wrote: > > > Hello, > I have a chicken and egg problem in the form of 2 projects in Eclipse that > are circularly dependant on each other. I cant publish either since they > both need the other (or its Ivy artifact) to compile. But to be able to > publish, I need to compile at least one so I am stuck here. > Can Ivy help this test case ? > thanks > Saurabh > > > -- > View this message in context: > http://www.nabble.com/chicken-and-egg-tf4261298.html#a12126536 > Sent from the ivy-user mailing list archive at Nabble.com. > >
