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/plugin.properti
es"/>
This overwrote any properties I was setting.
<maven:set /> is working fine.
ToddC
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
