The problem with cyclic dependencies in Maven is that you cannot build project A without having built project B, and you can't build project B without having A. This means that you will have trouble "bootstrapping" artifact generation of projects A and B in Maven. What you can do, is to use, for instance, an Ide that supports cyclic dependencies to generate the jar file for either project A or project B to get you started, and then making sure you do not do parallell development on project A and B without building a jar (SNAPSHOT) in between (or you will get the same problem as before).
I would recommend, though, that you create a new project C that depends on A and B, and put all the code from project A that depends on B, and all the code from project B that depends on A in it. This way you are free as a bird to do parallell development as you see fit. Cyclic dependencies lead to much trouble, so if possible you should, in my oppinion, try to avoid them. Hope this helps. Best Regards Bent On Fri, 29 Oct 2004 11:57:00 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Is there a way of getting maven to work in situation where there is a > cyclic dependency between project A and B? > > Jeff > > Registered Linux user number 366042 > > This e-mail is intended exclusively for the addressee. > If you are not the addressee you must not read, copy, use or disclose > the e-mail nor the content; please notify us immediately (by clicking "Reply") and > delete this e-mail. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
