Sorry i'm missed this mail 2008/11/14 Gilles Scokart <[EMAIL PROTECTED]>
> 2008/11/13 Gilles Scokart <[EMAIL PROTECTED]>: > > I'm +1 to put the concept in Ant's core, marked as experimental. > > > > A question that I have is how deep we want to push this concept? > > > > A first level would be that a phase or a target-group is a "normal" > > tartget for which the depends is build based on the other target that > > are found. (with that view, I wonder by the way what motivate the fact > > that the phase have no tasks). > IMHO target-group are more powerfull when depending on other target-groups. I think this kind of target should stay as abstract as possible. This allow you more flexibilty. > > > > A second level (maybe I go too far) might be to put it deeper up to > > the event notification. A build that use phase might have > > phaseStarted and phaseFinished event sent around targetStarted and > > targetFinished. > This could be interresting A third level (or 2bis) : what will be the meaning if the if/unless > attribute on a phase ? > With the simple aproach in which phase are 'simple' targets, it does > nothing. But I think it would be more intuitice if that would mean > "do or skip all the target bound in that phase. As target-group is nothing more than a "target" so if/unless attribute is supported. Exemple <project> <target-group name="test" depends="other-targetgroup" description="..." unless="skip.test"/> <target name="myTestTarget" depends="whatever" phase="test"> ... </target> </project> By typing "ant test" you will execute ALL target related to test target-group By typing "ant test -Dskip.test=true" you will not execute any target related to test target-group. In opposite, if you wanna execute explicitly "ant myTestTarget", phase attribute is ignored (so skip.attribute should not be applied). Jean Louis
