On 3/25/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
What is exactly the purpose of the undocumented (unused and untested)
It's a lot of 'un-' :-) task IvyCheck ? I think IvyCheck was written in one of the very first Ivy version, maybe before the first public version, and never removed from the code even if it never "graduated" to a used, tested and documented task :-) Its purpose is to check the consistency of a module in a repository: check if its dependencies are availalble with proper configurations, and check that artifacts published by the module are available. I've used it a long time ago to check the consistency of a filesystem repository, with an antcontrib:for task to iterate over all ivy files of the repository. If there is any trouble maintaining it, we can simply remove it, since it has never been documented. - Xavier - Xavier --
Gilles SCOKART
