[
https://issues.apache.org/jira/browse/IVY-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326263#comment-17326263
]
Maxime Andrighetto commented on IVY-1629:
-----------------------------------------
In my case, a better workaround than cleaning all the cache is to use
ivy.resolver.default.check.modified before the configuration of Ivy.
However one might want to call ivy:info after the configuration of ivy...?
> Add attribute to force ivy:info not using the cache
> ---------------------------------------------------
>
> Key: IVY-1629
> URL: https://issues.apache.org/jira/browse/IVY-1629
> Project: Ivy
> Issue Type: Improvement
> Reporter: Maxime Andrighetto
> Priority: Major
>
> Info retrieved from the cache is sometimes different than from the real Ivy
> repository. Currently the solution is to clean cache prior to executing
> ivy:info, but this defeats the purpose of the cache for other tasks...
> Please add an attribute to force not use the cache when calling ivy:info (the
> same attribute may be used by 'resolve' or other post resolve tasks btw).
> This would be really helpful!
> Thanks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
