Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (herse.apache.org: domain of steve.loughran@gmail.com
 designates 64.233.184.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=RiK13yMOPwK4RPiwDOelUBuljdfVtciEdxjVMuXz7ccI4omI/wcXcIq0/fKXNkW9GCjugJ74z/b/OcD4HoGO5wDv+Y5gBO551gVRbJDrqlTJfUd/WuwDGt7SFSFxXbFD7Wbz6Igj66L6C0/P76kYub33C5FQkjMLsSyD7rUz3SQ=
Message-ID: <c84a50780705220324x679528e8o1f7c36400a594f9c@mail.gmail.com>
Date: Tue, 22 May 2007 11:24:39 +0100
From: "Steve Loughran" <steve.loughran@gmail.com>
To: repository@apache.org
Subject: Re: what does ${version} do in a POM
In-Reply-To: <635a05060705220214j1e419893h1cbaac8048adb8fb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c84a50780705210743u19bdb9b1x7c6b84d879857e0e@mail.gmail.com>
	 <adba96190705210855l1996c7d0xba68e8a20e6ff94f@mail.gmail.com>
	 <262c6c680705211842s2c7b84cap93ba67d467b904ea@mail.gmail.com>
	 <c84a50780705220134n626f5cc1q5ef232e51e20d04c@mail.gmail.com>
	 <635a05060705220214j1e419893h1cbaac8048adb8fb@mail.gmail.com>

On 22/05/07, Xavier Hanin <xavier.hanin@gmail.com> wrote:

> BTW I agree with steeve, published metadata should be self contained
> with no reference, it would make tool development much easier and much
> more stable and reproducible. It's nice to know this has been done in
> maven 1.1.


If you were to be fully rigorous, you'd do a complete closure of the
dependency graph, so the metadata of every artifact would list the
dependencies as resolved by the build tool at the time of release.
That way you don't have to "think like a turtle" and reimplement the
resolution logic of the specific tool used just to get the
dependencies. It would also be a nice regression test for resolution
code...if you resolved the pom and came up with something different
from the closure, you'd know your algorithm was broken.

-steve