> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 22 April 2004 07:41 > To: 'Maven Developers List' > Subject: RE: [Q] Setting a property so that it's visible from another > plugin > > We should create a set tag as well I guess.
Yep. That would be great. Only problem with this (as with pluginVar - which is not too well named BTW if we add a set tag) is that plugins who uses it will not be compatible with previous Maven versions... > > If you just want to load the plugin, I think you need to do the depedency > handle. We ended up deciding this was the best way rather than using > dependencies on dummy goals (like war:load). > > I know you know how this works because cactus has a dependency handle :) Yeah, I had to add it, but it was a bit of magic to me... ;-) Thanks -Vincent > > - Brett > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 22 April 2004 3:34 PM > > To: 'Maven Developers List' > > Subject: RE: [Q] Setting a property so that it's visible from > > another plugin > > > > > > > > > > > -----Original Message----- > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > Sent: 22 April 2004 01:38 > > > To: 'Maven Developers List' > > > Subject: RE: [Q] Setting a property so that it's visible > > from another > > > plugin > > > > > > 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). > > > > > > > ok thanks. I'll try this. > > > > Do you know why the <j:set var="maven.abbot.src.files" > > value="${infile}" > > scope="parent"/> doesn't work. The parent scope should point > > to a Jelly > > context inherited by both plugins, no? Maybe I need to do a > > findVariable() instead of getVariable() to get the property from the > > called plugin. I will try this too. > > > > > 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. > > > > Yep, but this is only to get properties, not to set them. Do > > you that I > > could use it indirectly to load the plugin? > > > > Thanks > > -Vincent > > > > > > > > - 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] > > > > > > > > > > --------------------------------------------------------------------- > > 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]
