On 10/8/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
> I'm not sure what you are asking... or why I'm being ping'd :-P

Sounds like you had the same problem before, so I'm just wondering if
you found a solution.
>
> Awhile back I was trying to get a plugins params to not be replaced
> at all, which I was told was impossible.  I'm not sure that is what
> you are looking for here.

Exactly. The weird thing is .... it worked :) I've been using this for
a couple of weeks and suddenly a user reported that the last snapshot
broke that functionnality.

I don't get why it's impossible. Plexus components are responsible to
inject the pom's value into the mojo's field right? What if we provide
a component that does not interpolate the content of the attribute. It
used to be like this at least? (maybe an older version of the plugin
plugin generates different descriptors?)

How did you solve this problem?

Thanks,
Stéphane

>
> Um, maybe you can jog my memory?
>
> --jason
>
>
> On Oct 7, 2007, at 10:18 AM, Stephane Nicoll wrote:
>
> > Ping.
> >
> > On 10/4/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> >> Anyone?
> >>
> >> On 9/13/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> >>> Jason D.?
> >>>
> >>> On 9/12/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> >>>> I think I remember Jason Dillon having a similar issue with the
> >>>> groovy stuff.
> >>>>
> >>>> -----Original Message-----
> >>>> From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
> >>>> Sent: Wednesday, September 12, 2007 3:33 AM
> >>>> To: Maven Developers List
> >>>> Subject: Not replacing token in plugin's parameters
> >>>>
> >>>> Hi,
> >>>>
> >>>> In the trunk of the war plugin, the artifacts can be packaged in
> >>>> WEB-INF/lib with a custom name, a la assembly plugin. This leads
> >>>> to a
> >>>> config like this for instance:
> >>>>
> >>>> <outputFileNameMapping>
> >>>>   ${artifactId}.${extension}
> >>>> </outputFileNameMapping>
> >>>>
> >>>> This worked for a while and "suddently" (that's the weird thing) it
> >>>> stopped. The reason for that is maven "now" (?) resolves the tokens
> >>>> before injecting the value in the plugin (so for instance foo.null
> >>>> where foo is the artifactId of the current project instead of
> >>>> ${artifactId}.${extension}).
> >>>>
> >>>> Questions:
> >>>>
> >>>> - I can reproduce with Maven 2.0.5, 2.0.6 and 2.0.7 so it's
> >>>> something
> >>>> related to the plugin generation maybe?
> >>>> - I am wondering if I could add a tag on field-level to disable
> >>>> this
> >>>> automatic resolution
> >>>>
> >>>> Any advice, thoughts?
> >>>>
> >>>> Thanks,
> >>>> Stéphane
> >>>>
> >>>> [1] http://jira.codehaus.org/browse/MWAR-116
> >>>> --
> >>>> Large Systems Suck: This rule is 100% transitive. If you build one,
> >>>> you suck" -- S.Yegge
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Large Systems Suck: This rule is 100% transitive. If you build one,
> >>> you suck" -- S.Yegge
> >>>
> >>
> >>
> >> --
> >> Large Systems Suck: This rule is 100% transitive. If you build one,
> >> you suck" -- S.Yegge
> >>
> >
> >
> > --
> > Large Systems Suck: This rule is 100% transitive. If you build one,
> > you suck" -- S.Yegge
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck" -- S.Yegge

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to