maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Allen (JIRA)" <>
Subject [jira] Commented: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated
Date Sun, 08 Jan 2006 11:52:01 GMT
    [ ] 

John Allen commented on MNG-1943:


re 'a rare case', obviously my familiarity with these internal APIs and there usage is greatly
limited so I will defer to your expertese but in general I would have thought that if someone
is using an accessor to retreive a value they will want the cooked version of that 'property'
and not an internal/meta representation of it, after all what use is ${} to the developer
who has called getUrl()? 

I'll keep a keen eye out for your MSITE-71 code as I have a number of plugins that i've had
to make reactor dependent in order to gain access to properly interpolated parent model data.

re 'integration tests' - yep, thats exactly what i meant :) 

> MavenProject::getParent() returns a MavenProject that is NOT interpolated
> -------------------------------------------------------------------------
>          Key: MNG-1943
>          URL:
>      Project: Maven 2
>         Type: Bug

>     Reporter: John Allen
>     Priority: Blocker

> Plugin developers repeatedly use ${project}.getParent().someMethod() yet getParent()
returns a project that has not been interpolated. This obviously needs to be fixed but may
I also suggest that all plugin acceptance testing is revisted to ensure that the tests use
POMs that are littered with property expressions and not literals.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message