[GitHub] ant-ivy pull request #:

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ant-ivy pull request #:

bodewig
Github user twogee commented on the pull request:

    https://github.com/apache/ant-ivy/commit/9b2165894ef23247d658dd37e93161c1a59b1c65#commitcomment-23498086
 
    What else must be done to remove it? Deprecate the class?
   
    Here's the [relevant discussion](http://www.mail-archive.com/ivy-user@.../msg00441.html) which refers to a [JIRA issue](https://issues.apache.org/jira/browse/IVY-612) attempting to document it. In particular, Xavier Hanin stated
   
    ```
    CacheResolver has been introduced quite a long time ago and never
    documented because it wasn't supposed to be public. I'm still not sure
    it's a good idea to use it... IMO, Ivy caching mechanism should be
    strong enough to avoid the requirement for a cache resolver, at least
    at resolve time. With the addition of dynamic revisions caching in
    beta 2, now Ivy cache has all information necessary to be able to
    perform a resolve from the cache, without actually requiring to use
    the cache resolver. This may require some improvement, like accepting
    to use dynamic revision resolution cached data even when they have
    exceeded their TTL. This could be a special resolve mode or refresh
    mode. With this improvement, the last thing for which the cache
    resolver would still be useful is publishing. But even in this case,
    I'd prefer using a local repository with useOrigin="true": the
    behavior is sligthly different, but I think this should address all
    the needs covered by cache resolver which only has its root in bad
    caching support and is a design flaw.
    ```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]