-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Are you sure that the child pom.xml files declare a parent of the top-level pom? You should refer to the parent pom by groupId, artifactId, and version. Maven will automatically search for ../pom.xml if you only build a child project, or you have the option of adding <relativePath>../somewhere-else/pom.xml</relativePath> to the parent declaration.
If you always want them inherited, you should put them in the parent's dependencies section. If you want to enforce specific attributes about a dependency - like version - across all child projects, use dependencyManagement, coupled with a dependency declaration in the child POM that only has groupId/artifactId and local overrides. HTH, john Alvarado, Juan wrote: | I have one project with three modules. A dependency might be needed in more | than one module. If I add that dependency to my top level pom.xml, the | modules below do not pick it up. I was under the impression that given | maven's inheritance capabilities I would be able to do this. What I want to | avoid is having to repeat the same dependencies in different pom.xml files. | | Thanks in advance, | | Juan A. | | | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDTT7lK3h2CZwO/4URAgDgAJ9r7sU68qM5EUViHguZlR4IqV7hFgCfTv7t jWLRwZk3gDPjXiiuK2qww5A= =ZgkK -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
