www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud HERITIER" <aherit...@gmail.com>
Subject Re: what does ${version} do in a POM
Date Tue, 22 May 2007 01:42:03 GMT
It's now solved with recent maven 1.1 version. When a pom is published, all
variables are resolved.
But oldest POMs are always incorrect...

Arnaud

On 21/05/07, Wendy Smoak <wsmoak@gmail.com> wrote:
>
> On 5/21/07, Steve Loughran <steve.loughran@gmail.com> wrote:
>
> > I ask, as Ivy bug#512: https://issues.apache.org/jira/browse/IVY-512
> >
> > shows that Ivy cannot load POM files which have references to a
> > ${version} variable, which appears to be the case in Cargo
> >
> > 1. is ${version} a built in variable, if so, what does it map to.
>
> It's the same as ${project.version} or ${pom.version}.  It might have
> been brought forward from Maven 1.
>
> > 2. where is the complete resolution process of maven2 defined, either
> > in text or in a test kit?
>
> I usually look here and add things as I discover them...
> http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
>
> --
> Wendy
>



-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.org
www.apache.org | maven.apache.org
...........................................................

Mime
View raw message