On 14/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > But how does that help in the situation where you declare dependencies > A and B, but both declare a dependency C at the same level? Is C > first, second or third when ordered? > > I haven't looked at this issue, but an application should avoid > classpath ordering at all costs.
I agree classpath ordering is not ideal, but I think an order should be enforced so that mvn is deterministic. The real-life scenario I was encountering was a same-named resource being loaded from one dependency jar rather than the intended dependency jar. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
