Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 6774 invoked from network); 27 Feb 2008 19:16:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 19:16:10 -0000 Received: (qmail 21108 invoked by uid 500); 27 Feb 2008 19:16:05 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 20925 invoked by uid 500); 27 Feb 2008 19:16:05 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 20916 invoked by uid 99); 27 Feb 2008 19:16:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 11:16:05 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [87.118.102.170] (HELO km10614-05.keymachine.de) (87.118.102.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 19:15:19 +0000 Received: from sbs173 (cm66-147.liwest.at [212.241.66.147]) by km10614-05.keymachine.de (Postfix) with ESMTP id C2B0B2C5265A for ; Wed, 27 Feb 2008 20:15:40 +0100 (CET) Date: Wed, 27 Feb 2008 20:15:45 +0100 From: Harald Braumann To: ivy-user@ant.apache.org Subject: Re: specify versions separate from dependencies Message-ID: <20080227201545.20c3336d@sbs173> In-Reply-To: <745B9EDF57802349B13F90E4E0B4B86C3B9F1D585E@HOUEXCH012.corp.halliburton.com> References: <635a05060802270617i57bf3697t80968959e8349e1b@mail.gmail.com> <24048DC1F8522C44B83040006BCC8FC370A572@troy.bmi.ohio-state.edu> <20080227183538.1ae0a0c6@sbs173> <635a05060802271002h75b24c39kddde5d8dae6c2d19@mail.gmail.com> <20080227194947.4f103415@sbs173> <745B9EDF57802349B13F90E4E0B4B86C3B9F1D585E@HOUEXCH012.corp.halliburton.com> X-Mailer: Claws Mail 3.3.0 (GTK+ 2.12.5; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/0WJvaB=oKG52SbXfqYVbSMn"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Virus-Checked: Checked by ClamAV on apache.org --Sig_/0WJvaB=oKG52SbXfqYVbSMn Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 27 Feb 2008 12:57:04 -0600 Shawn Castrianni 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 > 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. >=20 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. >=20 > --- > Shawn Castrianni harry --Sig_/0WJvaB=oKG52SbXfqYVbSMn Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHxbbiwMFqDB+mz24RAkBXAJ4jM7IzsN6yPl5CWoH4VIT8UovPygCgnszq v90C3ffeKKZwf1KzeDb+zcg= =UQra -----END PGP SIGNATURE----- --Sig_/0WJvaB=oKG52SbXfqYVbSMn--