This is essentially why the <dependencyManagement> node was created. Take a look at it.
You'll probably want to make a single corporate-wide "super parent" that all your projects point to, and include the <depMgmt> node in that pom. Then in projects that need to use various dependencies, you can declare the dependency without any version information and it will use the version declared in the super parent <depMgmt> node. Wayne On 11/3/06, jp4 <[EMAIL PROTECTED]> wrote:
I have a client with many different maven projects. I am trying to figure out a way to manage the versions of common libraries across these projects without duplicating the version number in each project. For example, commons-lang-1.1.jar is used in 50 projects. I know that I can use a parent pom file to do this, but I don't want all of my projects to include everything in the parent pom. Is there a way to import or include a dependency in your pom... So for example, define a file with common-lang dependency and include that in all pom files that need to reference it? Thanks, jp4 -- View this message in context: http://www.nabble.com/Mechanism-to-import-common-depdencies-into-your-pom-files--tf2568584s177.html#a7159759 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
