On Wed, 7 Jul 2004 15:03:51 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'm sure the answer to this will be "don't do it like that", but here > goes... > When would you ever get a response like that on a Maven list? :)
Anyway, I think the answer is to add scope="parent" to your <j:set/>. However, instead of this, I would put the parent maven.xml's code into a new plugin and then use maven:get/maven:set on the plugin to address the variable. Much more reliable and future-proof. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
