[ 
https://issues.apache.org/jira/browse/IVY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611257#action_12611257
 ] 

Xavier Hanin commented on IVY-479:
----------------------------------

There has been some progress on this, since it is now possible to set a TTL for 
dynamic revision resolution, so that Ivy reuse the same dynamic revision 
resolution for a while. So now by properly your TTL you can make this work if 
you plan to be offline. But it isn't as good as providing a real fallback. 

If you want to implement this, I suggest having a look at how 
DefaultRepositoryCacheManager is implemented and deals with TTL. The problem is 
that the cache doesn't know if there is a network connection or not. So you 
will also have to change BasicResolver to ask the Cache to resolve the dynamic 
revision again, maybe with a special parameter. And you may need to keep 
resolved dynamic revision information longer than the TTL just in case you 
loose network connection. Or you could delegate to CacheResolver when you find 
out that network connection has been lost.

> Latest Strategies does not work in off-line situations.
> -------------------------------------------------------
>
>                 Key: IVY-479
>                 URL: https://issues.apache.org/jira/browse/IVY-479
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.4.1
>         Environment: Fedora Core 6
> Ant 1.6.5
>            Reporter: Matt Inger
>
> When resolving something like the following:
> <ivy:cachefileset setid="my.fileset" organisation="apache" module="log4j" 
> revision="latest.integration" inline="true" />
> OR
> <ivy:cachefileset setid="my.fileset" organisation="apache" module="log4j" 
> revision="1.2.+" inline="true" />
> This works fine if I am connected to the network.  However, if I disconnect 
> from the network, it no longer
> functions properly, eventually timing out on the URL resolvers configured in 
> my ivyconf.xml file.  If i replace
> the "revision" with an absolute revision (such as "1.2.8") this works just 
> fine when not connected to the network.
> In my opinion, if you cannot connect to the network, the latest strategies 
> should be able to fall back to computing
> the latest revision based on the cache only.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to