You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Heritier Arnaud <ah...@axway.com> on 2004/07/01 08:36:12 UTC
RE : How one plugin (using jelly) can set properties of another pl ugin
You set your properties in a post goal
<postGoal name="torque:init">
<maven:set />
</postGoal>
It should work.
Arnaud
> -----Message d'origine-----
> De : Todd Carmichael [mailto:toddc@concur.com]
> Envoyé : jeudi 1 juillet 2004 08:30
> À : 'Maven Users List'
> Objet : RE: How one plugin (using jelly) can set properties
> of another pl ugin
>
>
> Also, I found it necessary to call at least one goal in the
> plugin before setting properties in it.
>
> ToddC
>
>
> -----Original Message-----
> From: Todd Carmichael [mailto:toddc@concur.com]
> Sent: Wednesday, June 30, 2004 11:11 PM
> To: 'Maven Users List'
> Subject: RE: How one plugin (using jelly) can set properties
> of another pl ugin
>
>
> Found my problem. The Torque plugin I was calling had the
> following line in its torque:init goal in plugin.jelly
>
> <!-- The default.properties file will map old properties
> to the new ones along
> with setting the correct defaults.
>
> Note: I have no idea why this file is not already
> processed by the plugin..
> -->
> <property
> file="${maven.plugin.dir}/maven-torque-plugin-3.1-concur-dev/p
> lugin.properti
> es"/>
>
> This overwrote any properties I was setting.
>
> <maven:set /> is working fine.
>
> ToddC
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Wednesday, June 30, 2004 5:29 PM
> To: Maven Users List
> Subject: Re: How one plugin (using jelly) can set properties
> of another plugin
>
>
> <maven:set /> is preferred
>
> On Wed, 30 Jun 2004 14:54:10 -0700, Todd Carmichael <to...@concur.com>
> wrote:
> >
> > Basically, I am trying to write a plugin that calls another
> plugin and
> > I need one plugin to set properties for another. I see
> various ways
> > to do this using:
> >
> >
> pom.getPluginContext('maven-webserver-plugin').setVariable('foo','bar'
> > )
> > <maven:set plugin="maven-webserver-plugin" property="foo"
> > value="bar"/>
> >
> > Which is preferred? Is this syntax correct? Is the <id> of
> the plugin
> > used in these mechanisms? As you can tell I am having
> trouble getting
> > these to work. I am using RC3. Thanks.
> >
> > ToddC
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org