To get you started for Maven 2: http://maven.apache.org/maven2/dependency-mechanism.html#dependency_management
-Stephen On 10/14/05, Michael Böckling <[EMAIL PROTECTED]> wrote: > 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] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
