> Two potential solutions:
>
> 1) Instead of a build-all target, have one target each per <ant> or
<cvs>
> tag. The generated ant targets can depend on the cvs targets, and
you can
> use the "defined-in" attribute to locate the appropriate cvs
commands.
> There can also be a build-all target which depends on each ant
target.
> This is handy, as one thing I often do is build a single project.
>
> 2) You can use an defined-in to determine the project which contains
the
> cvs tag. If you are concerned about not wanting to invoke cvs
multiple
> times, you can do something like
test="not(previous::project[@name=$name])"
> to determine if this is first or not.
Will try it out. Thanks.
> In general having people coding their project definitions knowing
the order
> by which their projects may be included in a workspace is not a good
thing.
Agreed. Just wanted to move down the line and see if I wasn't beating
my head on a rock. I had no intention of keeping that syntax.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
