I'm having a huge problem this morning using the Maven ant tasks in a multi-module project that we're trying to release this morning. We use the Maven tasks to declare a dependency from within a Maven wrapped Ant build on a shared lib that is also part of the multi-module project. I understand that sounds confusing and complicated so let me put it this way. In one submodule of our multi-module build, Maven calls into an Ant build. This Ant build depends on another submodule in the same project. We pass in the project's pom version as an Ant property and use this in the artifact:dependency task to locate the jar. This all works just fine until we cut a release. The problem comes from artifact:dependency looking at the released version of the dependency's pom and trying to find its parent on our repo. Since it's in mid release the parent pom has not been deployed and the build fails breaking everything. I think the dependency task should have a way of knowing that the dependency is part of a multi-module build in the same project and locating it accordingly. Or maybe there's a better approach all together? Could some of you experts chime in? -- View this message in context: http://www.nabble.com/Maven-Ant-tasks-and-the-release-plugin%21-tp17626143p17626143.html Sent from the Maven - Users mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
