Try locking the version in both projects using <version>[1.1]</version> etc. Otherwise Maven might decide to use one version (or the other) for both builds, despite the different declarations.
Wayne On 5/15/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all, In a multi-project P, child #1 (cP1) runs before child #2 (cP2). In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in order to use ant-1.7.0 instead of ant-1.6.5). When running mvn install on P, the cP1 builds normally, but the cP2 fails because it uses the maven-antrun-plugin:1.1 instead of maven-antrun-plugin:1.1-INTERNAL :-( If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the dependencies from cP2, then everything works fine! Adrian. --------------------------------------------------------------------- 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]
