Scott Sanders wrote:
>
> Stupidly because as xml-stylboook2 is an option on jakarta-ant,
> it gets 'executed' before stylebook, so the cvs from xml-stylebook
> is not there yet. On xml-xalan2, xml-xalan1 gets executed first,
> so there are no problems there. Couldn' think of another way
> around at the moment, so that is what I ended up with...
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.
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.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
