I have a question that I hope isn't too basic. I've been trying to reconcile the behavior of dependency management with my expectations. I'll state in advance that I'm more than willing to admit that my expectations might be unrealistic.
We've got a "home grown" dependency mechanism that works as follows: If artifact A requires artifact B and artifact B does not exist it builds artifact B before building artifact A. To further clarify what I'd like to do, I had originally started with the <modules> element but quickly ran into this screnario: artifacts A and B are built in the same POM (<packaging>pom</packaging>), and both require artifact C. This does not make it past the reactor engine, which will not allow artifact C to appear more than once. Is this behavior possible with the <dependencyManagement> tags? So far it doesn't seem likely, but perhaps I'm not understanding dependency management, which brings us back to that start of this message. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
