I've been perusing a set of JIRAs linked to MNGECLIPSE-299, and they
all seem to describe variations on this theme.
This doesn't turn out to be about indirection, but about
${settings.localRepository}.
But I'm not sure what I'd report this against were I to build up a
repro. What JIRA-able component is responsible for substituting into
the XML when reading the POM and building up the PlexusConfiguration?
On Wed, Mar 2, 2011 at 7:10 PM, Benson Margulies <[email protected]> wrote:
> I would be ever-so-grateful if someone would tell me if the following
> is expected.
>
> Using maven 2.2.1 or 3.0.0.
>
> I have a plugin I built. One of its parameters is treated just as
> arbitrary XML: declared as PlexusConfiguration.
>
> In the XML of the example at hand, there is a use of a parameter
> reference. Call it ${a}.
>
> If I define <a>somevalue</a> in the current POM, it works fine. By the
> time my code walks the XML, the ${x} has been replaced by 'somevalue'.
>
> However, if ${a} is defined to be another parameter reference:
>
> <a>${settings.localRepository}</a>
>
> the literal string ${settings.localRepository} is what sticks around
> in the data seen inside the PlexusConfiguration object.
>
> Is this a surprise to any plexus gurus in the audience? Is it possible
> that I'm not asking the PlexusConfiguration object the right question?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
