maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <>
Subject RE: DuplicateProjectException
Date Fri, 19 Oct 2007 07:09:57 GMT
Heinrich Nirschl wrote on Thursday, October 18, 2007 6:12 PM:

> On 10/18/07, Jason Nerothin <> 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.

In case of a copy & paste error. Copy an existing sub project, add it to the multi project
build and forget to adjust the artifactId ... boom!


- Jörg

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message