From: Eric B. <er...@go...> - 2007-02-21 19:08:53
|
Jocelyn wrote: > I quickly made some changes and addition to geant to be able to have > <group /> task > the addition and changes are in the attached zip file. > > I could have commited it, but first I wanted to know your feeling about > this. > And ... I made small changes to geant to handle this, maybe this could > be better by having a common ancestor GEANT_GROUP > for GEANT_TARGET and GEANT_GROUP_TASK for instance ... > > But for now, my changes are safe and do not break any code. It is just > addition. > > So I'll wait for your comments, and if none, I guess I'll commit the > changes to the svn repository. > > an example is: > > <?xml version="1.0"?> > <project name="test_group" default="test"> > <target name="test" > > <echo message="test group..." /> > <input variable="cont" message="Continue ?" validargs="y,n" > defaultvalue="y" answer_required="true" /> > <group if="${cont}=y" > > <echo message="group started" /> > <echo message=" ### Select group ### " /> > <input variable="selection" message="Select a group (a|b|c)" > validargs="a,b,c" defaultvalue="a" answer_required="true" /> > <group name="A" if="$selection=a" > > <echo message="group A.1" /> > <echo message="group A.2" /> > <echo message="group A.3" /> > </group> > <group name="B" if="$selection=b" > > <echo message="group B.1" /> > <echo message="group B.2" /> > <echo message="group B.3" /> > </group> > <echo message="Group C" if="$selection=c" /> > <echo message="group terminated" /> > </group> > </target> > </project> How does it look in the schema? Is there a way to express that when <group> appears where a task is expected, then it should contain tasks. And when it appears in places where a foo is expected then it should contain foos, and not tasks. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |