On Wed, 27 Feb 2008 12:57:04 -0600 Shawn Castrianni <[EMAIL PROTECTED]> wrote:
> I like this whole discussion with the ability to more closely specify > transitive dependencies. However, I would add one more requirement. > I think this control should also be allowed to be specified in the > <modules> section of the settings file. This is very important when > you are in charge of an entire company's modules each with their own > release schedules and combination of modules and branches. I could > spend my time writing settings files for each product release with > complete control over what branch of what modules and even what > explicit revisions should be used. Then a given developer working on > a given product release would simply set an environment variable or > something to control which settings file to use. Then he > automatically gets the blessed configuration for that product > release. I don't want to have to go to each ivy file and make > changes all over the place which could easily result in branching > each module's source code just to get a new ivy.xml file. > Good point. I was just thinking about something along these lines. > This concept is very similar to Clearcase's config spec idea, except > I call it an Ivy Release Spec. > > --- > Shawn Castrianni harry
signature.asc
Description: PGP signature
