The way we do this in Maven 1.0.2 is to define a set of build properties called "lib.<whatever>.version" with the value of the property set to the version of <whatever> we are using. We then use these properties in place of the version number in the project.xml files. Since we use <extends/> to have a root project for all of our various projects, these variables can be placed in the project.properties file in the root project. If that is not feasible, you can place the properties in each user's configuration.
-----Original Message----- From: Michael Böckling [mailto:[EMAIL PROTECTED] Sent: Friday, October 14, 2005 08:22 To: Maven Users List Subject: [m1/m2] How to: central dependency management Hi guys, I have a not-so-technical question about dependency management in Maven (preferably m1, but m2 is okay also if m1 is impossible). Let's say, a new version of an important library (Jakarta Commons, JUnit etc.) has been released, and I'd like to update all my projects to use that library. Is there any way to configure the maven project setups in such a way that this only has to be done in one single place? The idea: - New version of a dependency has come out - Build-Manager says it looks good, and now he wants to update all projects that need the said dependency to use the new version. - Possibly also make sure only versions that are API compatible get updated - Is it possible to make it so that this dependency change only has to be done in one single place, and all projects pick it up automatically? This approach has the advantage to reduce the overhead that would otherwise be involved with upgrading. I'd be really thankful for suggestions on how to do this, as I couldn't find any informations on this topic. Regards, Michael Böckling --------------------------------------------------------------------- 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]
