I'm afraid that solution #1 will be hard to scale ... We have releases almost every day. Updating every other project every day doesnt seems to be such a good idea either ...
But thanks for your feedback ! On 07/01/2008, Barrett Nuzum <[EMAIL PROTECTED]> wrote: > Guillaume: > > At one of our clients, we had a very similar situation. > We opted to go with option #1, below. > > It *is* a bit of a maintenance burden, but it's far more reliable and > explicit than any alternatives. > > Barrett > > :: > Barrett Nuzum > Sr. Consultant > Direct: 918.640.4414 > Fax: 972.789.1340 > > Valtech Technologies, Inc. > 5080 Spectrum Drive > Suite 700 West > Addison, Texas 75001 > www.valtech.us <http://www.valtech.us/> > Delivering Business Agility > > > ________________________________ > > From: Guillaume Lederrey [mailto:[EMAIL PROTECTED] > Sent: Mon 1/7/2008 10:34 AM > To: Maven Users List > Subject: Dependency versions in large multi-projects multi-modules environment > > > > Hello ! > > I have to investigate the migration to Maven in our organisation. We > have a pretty large software base : about 100 projects each generating > 3 to 6 artifacts. A part of these modules are a framework used by most > other projects. > > For the moment, we are managing versioning with ant, and a script that > download the latest version of each library. This script is updated > every time a new version of a library is released. The script itself > is on a server and accessed by all developers / build tools. > > I see to major ways to do the same with Maven : > > 1) replace our script by a parent pom which will contain all > dependencies and versions in its <dependencyManagement/> section. This > means that every time a new library is released, a new version of this > parent pom has to be released as well. And all other projects have to > update their reference to the latest parent pom. > > 2) use version ranges in the parent pom. This way, the new version of > the library is used by all projects as soon as it is available in our > central repository. Much easier to manage, but it sound a bit scary to > have it that much automated ... Other problem, we will loose build > reproducibility ... > > I'll be happy to know how you manage dependency versions in large > organizations ... > > Thanks a lot ! > > Guillaume > > > -- > Jabber : [EMAIL PROTECTED] > Skype : Guillaume.Lederrey > Projects : > * http://rwanda.wordpress.com/ > * http://rwandatech.wordpress.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] > > -- Jabber : [EMAIL PROTECTED] Skype : Guillaume.Lederrey Projects : * http://rwanda.wordpress.com/ * http://rwandatech.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
