[
https://issues.apache.org/jira/browse/IVY-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877184#action_12877184
]
Maarten Coene commented on IVY-1195:
------------------------------------
ok fair enough, although I'm not convinced yet this should be a standard Ivy
resolver. I think the use-case is too limited for it at the moment.
But luckily, Ivy is very extensible and allows custom resolvers to be plugged
in very easily.
So maybe you could try to write such a resolver yourself? And if you think
others could find it useful as well, attach it to this issue or start a project
on sourceforge, googlecode, ... to share this resolver with the community (like
there is a similar project for an SVN resolver for instance)
> feature request: retrying resolver wrapper
> ------------------------------------------
>
> Key: IVY-1195
> URL: https://issues.apache.org/jira/browse/IVY-1195
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.1.0
> Reporter: Stepan Koltsov
>
> I'm requesting a retrying resolver.
> *description*
> Retrying resolver delegates resolution to configured child resolver. If child
> resolver fails, if requests child to perform a resolution again after some
> time.
> *example*
> {code}
> <resolvers>
> <retry name="default" timeout="5m" start="10s" exp="1.5">
> <svn .../>
> </retry>
> </resolvers>
> {code}
> In the example above, "default" resolver will try call SVN resolver to
> resolve dependencies, if SVN resolver fails, it will be called again after
> 10s, then after 15s, then after 27s, and so on, but not after 5 minutes after
> resolver start.
> *motivation*
> We have build server, that builds projects right after commit. Projects
> depend on concrete revisions of another projects, revisions are specified in
> ivy.xml (say, "app" depends on "lib"). Sometimes developers commit to
> dependent project "app" immediately after commit to the base project "lib".
> And in this case there is a high chance, that base project "lib" is not yet
> built (so artifact is not published) at the time of dependent project "app"
> ivy:resolve task run. So build of dependent project "app" fails.
> Retry task could resolve this situation: dependent project "app" build start
> will be delayed until completion of "lib" build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
