scope is a bit funny in the way we use jelly - sometimes this will work and sometimes it won't.
maven:set should work if you have already initialised multiproject by executing a goal or depending on a tag from it. However, your best bet might be to do the <j:set /> with scope="parent". - Brett On Mon, 28 Jun 2004 18:06:05 -0500, Jefferson K. French <[EMAIL PROTECTED]> wrote: > > I'm trying to move some common goals into an internal plugin. One of > them invokes multiproject:goal, but multiproject complains that the > goal property is not set, even though I set it before the call: > > <goal name="mdb:build-multi"> > <j:set var="goal" value="mdb:build-only"/> > <attainGoal name="multiproject:goal"/> > </goal> > > I verified with debug that 'goal' is not set in the plugin, but I > don't know why, since I do the j:set beforehand. Do I need to set > properties differently in a plugin? I also tried: > > <maven:set plugin="multiproject" property="goal" value="mdb:build-only"/> > > but with the same result. I'm running RC4 and Multiproject 1.3.1. > Thanks for any leads. > > Jeff > > -- > mailto:[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]
