Hmm, I always assumed that attainGoal would only call the referenced goal once, since it _is_ a goal, and once run, it should be considered 'attained'. But testing it out, you can invoke attainGoal multiple times with the same goal name and the goal contents will be run multiple times.

Now from this I guess I can conclude that for each invocation, Maven is throwing away the werkz goal session it used on the previous call. I think I am missing something here, but I would have thought maven would be using the same session throughout the entire invocation of the build. Can anybody clarify how this actually works? Is there a distinciton between goals called as a result of attainGoal, and goals called as a result of a dependency relationship?


Age Mooy wrote:

Isn't that what <attainGoal name="my:goal"/> is for ?

Age


-----Original Message-----
From: Colin Sampaleanu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 20:51
To: Turbine Maven Users List
Subject: What is maven/jelly equivalent of ant's antcall?


Ant's antcall task is sometimes used to do 'subroutine' style calls into other targets from one or more locations within an ant build file. To some extent this is not too clean since it mixes up usage of targets as run due to dependencies vs. targets run as subroutines, but it does work. I am trying to figure out the best way to do something similar in Maven/Jelly.

One way I can think that should work is to use Jelly's define:tag tag to define a new tag for the funtionality I need, and then just use that tag appropriately... Another way would be to use jeez:target to wrap a goal, and then use antcall to call it.

Anybody have any suggestions on the best way to do this?


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to