It is pretty bad. In 2.0.x, if I define url="http"//sonatype.org", then this
value will be applied to ${url}. If later, someone defines
project.properties.url = "foobar", in either the child or parent pom, then
${url} will resolve to foobar. So in one case ${url} is ${project.url}, in
another case it is project.properties.url.
So it looks like the rule in 2.0.x is: for some A that is a model element
name, if ${project.properties.A} exists, ${A} = ${project.properties.A} ,
else.${A}=${project.A}.
Shane
On Tue, Oct 14, 2008 at 7:54 AM, Brian E. Fox <[EMAIL PROTECTED]>wrote:
>
> >Since I currently cannot imagine a use case for this aliasing, I am +1
> >if the next model version would simplify/restrict the interpolation
> >semantics to not alias project.foo with foo.
>
> Same here but unfortunately this should be tied to the model version,
> otherwise a ton of stuff in central would suddenly be unusable.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
