Re: [m102] overriding goal
I see. So suppose there is a plugin goal named world:destroy and I only want to run it if the property evil.dictator is set. How would I do this? I don't want it to be an error if someone tries to run it without said property; I just want to silently do nothing. On the other hand, if that property is set, then I would like to run the plugin goal. From where I sit this seems to be impossible. Thanks, Laird On 2/7/06, Jörg Schaible [EMAIL PROTECTED] wrote: Hi Laird, Laird Nelson wrote on Tuesday, February 07, 2006 5:23 AM: Leaping in: if you can override a plugin goal, can you call super? That is, I'd like my goal override to prevent execution of the real goal in some circumstances. What's the best way to go about this? No. In that case you have to add your functionality to preGoal/postGoal. - Jörg Thanks, Laird On 1/13/06, Jörg Schaible [EMAIL PROTECTED] wrote: Kristof Vanbecelaere wrote on Friday, January 13, 2006 2:27 PM: Hi, is it correct that in 1.0.2 one can only override project goals but not plugin goals? No, you can also override plugin goals. - Jörg - 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]
Re: [m102] overriding goal
Laird Nelson wrote:
I see. So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set. How would I do this?
I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing. On the other hand, if that
property is set, then I would like to run the plugin goal.
From where I sit this seems to be impossible.
This is just from the top of my head so I haven't tried it but I think
this will work:
goal name=world:destroy
if test=${evil.dictator}
!-- destroy world --
/if
**/goal
If the property evil.dictator is set to true then the world is
destroyed when the goal is run.
HTH,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m102] overriding goal
Yes, thank you; you have, of course, defined a new goal that governs whether
the old one is executed, which is a perfectly valid approach. I was hoping
for a wee bit more, namely the ability to not only override a goal but to
gain access to the overridden goal from the overriding goal.
Thanks,
Laird
On 2/7/06, Henry S. Isidro [EMAIL PROTECTED] wrote:
Laird Nelson wrote:
I see. So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set. How would I do
this?
I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing. On the other hand, if that
property is set, then I would like to run the plugin goal.
From where I sit this seems to be impossible.
This is just from the top of my head so I haven't tried it but I think
this will work:
goal name=world:destroy
if test=${evil.dictator}
!-- destroy world --
/if
**/goal
If the property evil.dictator is set to true then the world is
destroyed when the goal is run.
HTH,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m102] overriding goal
Laird Nelson wrote:
Yes, thank you; you have, of course, defined a new goal that governs whether
the old one is executed, which is a perfectly valid approach. I was hoping
for a wee bit more, namely the ability to not only override a goal but to
gain access to the overridden goal from the overriding goal.
Thanks,
Laird
On 2/7/06, Henry S. Isidro [EMAIL PROTECTED] wrote:
Laird Nelson wrote:
I see. So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set. How would I do
this?
I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing. On the other hand, if that
property is set, then I would like to run the plugin goal.
From where I sit this seems to be impossible.
This is just from the top of my head so I haven't tried it but I think
this will work:
goal name=world:destroy
if test=${evil.dictator}
!-- destroy world --
/if
**/goal
If the property evil.dictator is set to true then the world is
destroyed when the goal is run.
HTH,
Henry
I'm not exactly sure what you mean but have you tried attainGoal name =
goalname /?
Regards,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m102] overriding goal
On 2/7/06, Henry S. Isidro [EMAIL PROTECTED] wrote:
I'm not exactly sure what you mean but have you tried attainGoal name =
goalname /?
To be fair, no, I haven't, but that would involve an infinite loop:
goal name=destroy:world
j;if test=${is.evil}/
attainGoal name=destroy:world/
/j:if
/goal
What I'd like to be able to do is:
goal name=destroy:world
j:if test=${not evil}
invokeOverriddenGoal name=destroy:world/
/j:if
/goal
But as is becoming more and more clear to me each day this is impossible.
Oh well; moving on.
Best,
Laird
Re: [m102] overriding goal
Laird Nelson wrote:
On 2/7/06, Henry S. Isidro [EMAIL PROTECTED] wrote:
I'm not exactly sure what you mean but have you tried attainGoal name =
goalname /?
To be fair, no, I haven't, but that would involve an infinite loop:
goal name=destroy:world
j;if test=${is.evil}/
attainGoal name=destroy:world/
/j:if
/goal
What I'd like to be able to do is:
goal name=destroy:world
j:if test=${not evil}
invokeOverriddenGoal name=destroy:world/
/j:if
/goal
But as is becoming more and more clear to me each day this is impossible.
Oh well; moving on.
Best,
Laird
I guess you're right, this might not be possible.
Regards,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m102] overriding goal
Leaping in: if you can override a plugin goal, can you call super? That is, I'd like my goal override to prevent execution of the real goal in some circumstances. What's the best way to go about this? Thanks, Laird On 1/13/06, Jörg Schaible [EMAIL PROTECTED] wrote: Kristof Vanbecelaere wrote on Friday, January 13, 2006 2:27 PM: Hi, is it correct that in 1.0.2 one can only override project goals but not plugin goals? No, you can also override plugin goals. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m102] overriding goal
Hi Laird, Laird Nelson wrote on Tuesday, February 07, 2006 5:23 AM: Leaping in: if you can override a plugin goal, can you call super? That is, I'd like my goal override to prevent execution of the real goal in some circumstances. What's the best way to go about this? No. In that case you have to add your functionality to preGoal/postGoal. - Jörg Thanks, Laird On 1/13/06, Jörg Schaible [EMAIL PROTECTED] wrote: Kristof Vanbecelaere wrote on Friday, January 13, 2006 2:27 PM: Hi, is it correct that in 1.0.2 one can only override project goals but not plugin goals? No, you can also override plugin goals. - Jörg - 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]
[m102] overriding goal
Hi, is it correct that in 1.0.2 one can only override project goals but not plugin goals? thanks, Kristof - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m102] overriding goal
Kristof Vanbecelaere wrote on Friday, January 13, 2006 2:27 PM: Hi, is it correct that in 1.0.2 one can only override project goals but not plugin goals? No, you can also override plugin goals. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
