On 10/18/07, Jason Nerothin <[EMAIL PROTECTED]> wrote: > Okay, so what I mean is that I have four complilation units: Unit A has > compile-time dependencies on B1 and B2 which in turn have a compile-time > dependency on unit C. "mvn compile" tries to figure out "which" code to link > against (B1->C or B2->C) and throws a DuplicateProjectException. Is such an > arrangement possible with maven or am I missing some larger point about > dependency management?
The situation you describe is normally handled without any problem. In fact it is quite common that dependencies have common sub-dependencies, just think of C being a logging package for example. I don't know in which situations Maven throws a DuplicateProjectException (never saw this one myself). Its maybe easier to diagnose the problem if we see the poms. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
