Here's a relevant discussion [1] with Xavier himself explaining the reason
for cache resolver being there.
[1]
http://apache-ivy.996301.n3.nabble.com/Does-Ivy-really-have-a-cache-resolver-td3648.html
Gintas
P.S. It's unrelated, but, while researching, I came across this issue:
[1] https://githu
Perhaps another JIRA issue [1] would cast some light?
[1] https://issues.apache.org/jira/browse/IVY-1227
Gintas
2017-07-27 18:10 GMT+02:00 Jaikiran Pai :
>
> On 27/07/17 9:34 PM, Jaikiran Pai wrote:
>
>> There's a JIRA[2] asking for the docs to be updated to explain this
>> resolver.
>>
>> ...
On 27/07/17 9:34 PM, Jaikiran Pai wrote:
There's a JIRA[2] asking for the docs to be updated to explain this
resolver.
...
[2] https://issues.apache.org/jira/browse/IVY-804
I meant this JIRA which asks for it to be documented
https://issues.apache.org/jira/browse/IVY-612
-Jaikiran
There's this JIRA issue https://issues.apache.org/jira/browse/IVY-804
where the user reports a genuine bug in our typedef.properties file
where we list the "cache" property twice with different values. Once to
consider the element as a resolver and the other to consider
the element as the cac
