forums2...@gmail.com]
Gesendet: Montag, 17. Juli 2017 06:56
An: dev@ant.apache.org
Betreff: Re: Proposed changes for IVY-735 - Ability to specify timeouts
I think, that's actually a good idea. Defining the timeout constraints
separately as named constraints and then referencing them would allow
reu
gt;
>
>
>
>
>
>
>
> Jan
>
>
> > -Ursprüngliche Nachricht-
> > Von: jai.forums2...@gmail.com [mailto:jai.forums2...@gmail.com]
> > Gesendet: Montag, 17. Juli 2017 06:56
> > An: dev@ant.apache.org
> > Betreff: Re:
> An: dev@ant.apache.org
> Betreff: Re: Proposed changes for IVY-735 - Ability to specify timeouts
>
> I think, that's actually a good idea. Defining the timeout constraints
> separately as named constraints and then referencing them would allow
> reusing these values
I think, that's actually a good idea. Defining the timeout constraints
separately as named constraints and then referencing them would allow
reusing these values on whichever resolvers want to:
read-timeout="">
...
-Jaikiran
On 14/07/17 10:33 PM, Gintautas
my €.02 : currently, all resolvers only have artifact patterns as child
elements, so I'd rather have the timeouts as attributes that might use
references, similarly to cache managers or latest strategies. That would
imply a global default that may be overridden individually.
Gintas
2017-07-14
https://issues.apache.org/jira/browse/IVY-735 is a feature request where
the users have asked for relevant timeouts while dealing with downloads.
A few weeks back we had a very brief discussion in an unrelated mail
where it was proposed that we allow configuring these timeout all the
way from
https://issues.apache.org/jira/browse/IVY-735 is a feature request where the
users have asked for relevant timeouts while dealing with downloads. A few
weeks back we had a very brief discussion in an unrelated mail where it was
proposed that we allow configuring these timeout all the way from
