ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bhatia <Bha...@OFAC.CH>
Subject Re: chicken and egg
Date Mon, 13 Aug 2007 14:47:24 GMT

Yes, I fully agree with you that its a bad design; actually the worse one.
But, I have 2 projects in different branches in CVS dependant on each other.
Currently, we are using WSAD/Eclipse to compile projects in the Eclipse IDE
workspace but that requires us to cvs co all dependant projects in the
workspace to compile them. To recover from this problem, we launched an
initiative to use Ivy in the Eclipse workspace.
The problem now is that I need to compile first to be able to publish and I
need published artifacts to compile either of them.
I will try to push for change of design to a saner one but if this has been
the norm rather than the exception, even Ivy cant help such a case I guess.

Tjeerd Verhagen wrote:
> 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 <> 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:
>> Sent from the ivy-user mailing list archive at

View this message in context:
Sent from the ivy-user mailing list archive at

View raw message