While plugin.getPluginContext works, it relies on the plugin being initialised. You can do that by declaring a dummy tag in the plugin (the dependency handle, and most importantly, adding the uri to your names space in the calling plugin).
An easier way is to use maven:pluginVar as it will initialise the plugin if it hasn't been already and you can avoid the dependency handle bit altogether. - Brett > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Thursday, 22 April 2004 12:58 AM > To: 'Maven Developers List' > Subject: [Q] Setting a property so that it's visible from > another plugin > > > Hi, > > I used to know how to do this but somehow it's not working > anymore for (I'm using RC3). I have 2 plugins one of them is > calling the other through attainGoal. The calling plugin also > sets a property that is supposed to be visible from the other plugin. > > I've tried without success the following: > > <j:set var="maven.abbot.src.files" value="${infile}" scope="parent"/> > > and > > ${plugin.getPluginContext('maven-abbot-plugin').setVariable('m > aven.abbot > .src.files',infile)} > > In the called plugin I simply do an echo like this: > > <echo>value = ${maven.abbot.src.files}</echo> > > The result is "value = " (i.e. no value printed). > > Any idea? > > Thanks > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
