Hi Martin, thanks for your hint to the <pluginManagement> section.
But actually, that is not exaclty what i want. Since i do not want to repeat defining each common dependency separately for each sub-module. This approach would be ideal, if i want to use this dependency in many sub-modules (but not all), so i could skip the definition in those sub-modules, where i do not need it. If a want to have a new common dependecy which shall be used for all sub-modules, i could simply add this dependency to the parent-pom, right? Why would i rather put in it each module individually, what would be the benefits? And why not put it into the core module (e.g. sandbox-core) , since all other sub-modules would use the core anyway? br R.C. -- View this message in context: http://maven.40175.n5.nabble.com/where-to-put-common-dependecies-in-multi-module-project-tp4931654p4931809.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]
