Robert Smith wrote:
Hi Steve,
Yes, I'm aware of it, its on the general list of "abuses of Ant", but on
the mild scale compared to GridAnt or (possibly) Askalon.
Ouch! Where can I find this list, and what can I do to get off of it?
Its in my head. All you have to do is remember that ant is a build tool,
not a generic workflow system designed for multi-day use across a farm
of machines.
If its just the logger, dont you really need a special remote task
logger instead of trying to use local classes as proxies for the distant
ones.
Possible. I do seem to recall that there was a (seemingly) valid
reason to do it this way at the time.
Or, we tune XmlLogger to store things differently, perhaps by
giving every task/target a unique ID, which could just be a number
allocated by a synchronized counter.
Yes. This would probably be the easiest, and safest solution.
well, contribs in that area would be best all round, I think.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
