Re: Ivy old docs removed - documentation now resides under asciidoc

I converted them, and they're dev-related. You can read them directly on GitHub :-) Gintas 2018-03-13 16:06 GMT+01:00 Jan Matèrne (jhm) : > May /docs-to-convert ;) > > A directory /doc makes the expectation to find (actual) documentation. > > > Jan > > > -Ursprüngliche

AW: Ivy old docs removed - documentation now resides under asciidoc

May /docs-to-convert ;) A directory /doc makes the expectation to find (actual) documentation. Jan > -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > Gesendet: Dienstag, 13. März 2018 10:14 > An: Ant Developers List > Betreff: Re: Ivy old docs

Re: User implementations of custom interfaces can have access to Task instance?

On 2018-03-13, Jaikiran Pai wrote: > I'm looking for some suggestion on whether it's a good/bad idea to > expose a method to custom user defined classes which takes a "Task" > object. This is in context of the JUnitLauncher task that I recently > added. It allows custom report

Re: Ivy old docs removed - documentation now resides under asciidoc

There is some documentation that has not been converted to asciidoc (eg ideas.txt or conflict-solving-algo.html). I will put them into dev, or does anyone have a better idea? Gintas 2018-03-07 11:49 GMT+01:00 Jaikiran Pai : > A while back we moved Ivy's documentation

User implementations of custom interfaces can have access to Task instance?

I'm looking for some suggestion on whether it's a good/bad idea to expose a method to custom user defined classes which takes a "Task" object. This is in context of the JUnitLauncher task that I recently added. It allows custom report formatters/listeners to be implemented and the expectation