This problem seems similar to mine: http://www.nabble.com/running-optional-ant-tasks-with-maven-antrun-plugin-td15842721s177.html
Why is the parent pom not seeing the plugin dependencies of a required jar module? greenstar wrote: > > Hello, > > I have a situation where dependencies of type "pom" are not found in the > reactor (ie: multi-module builds). If the dependency is of type "jar", > then it is found in the reactor with no problems. What is special about > "pom" types in the reactor? > > As an aside, the reason I am depending on a "pom" type is because I use > this for a bundling mechanism to group common sets of dependencies that > are included in other artifacts over and over again. We can't use the > <dependencyManagement> parent mechanism because we already use the single > inheritance for another orthogonal concern. Using pom bundles works well > except for the fact that dependencies of this type are not found in the > reactor. Am I abusing poms by using them this way? Is there a better way > to group dependencies without using the parent's <dependencyManagement> > mechanism? I could also just change the type of these bundles to type > jar. This works fine. It produces a small empty jar artifact which is > fine, but this seems a bit hackish. > > Thanks for your time. > > -- View this message in context: http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15951029.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]
