> I can understand a second compile for the clover plugin due 
> to the nature of what it's doing, but the other two have no 
> reason to have a unique session (that I know of).  Also, is 
> there some way I could detect that we're coming in for a 
> second round of compiling (in the case of the clover plugin) 
> and avoid doing my logic?

You could put a variable inside your preGoal to flag it is done, then check
for it later. Certainly an ugly workaround.
I don't see what the code is that can't be run twice (except for efficiency
reasons).

> 
> > We need to be wary of introducing new behaviour late in the
> > 1.0 RC cycle. A lot of people may have worked around this in 
> > their own way that could break.
> 
> I understand...so is this scheduled to be broken later, then? 
>  ;)  If anyone has any of these workarounds that they can 
> share, I'd be more than happy to use one of them.

I'm comfortable with changing things for the better in 1.1 and documenting
the way to fix up your own plugins in accordance with those changes.

One thing with this instance is though, that I'm not sure it's the right
thing to do. It seems to me that attainGoal should always run it again, and
prereqs only need be attained once.

- Brett

Reply via email to