This turned out to be a relatively smaller task than what I had
previously thought it would be. That's mainly thanks to the way this
whole interaction with the library, in Ivy, has been designed and kept
isolated from majority of the code.
So as of late yesterday, the master branch now uses 4.
> Le 24 juil. 2017 à 08:19, Jaikiran Pai a écrit :
>
> That's a a big enough reason to move to HttpComponents Client 4.x version!
> I'll have that done in this release of Ivy then.
+1
Nicolas
>
> -Jaikiran
>
>
> On 24/07/17 11:43 AM, Stefan Bodewig wrote:
>> On 2017-07-24, Jaikiran Pai wr
That's a a big enough reason to move to HttpComponents Client 4.x
version! I'll have that done in this release of Ivy then.
-Jaikiran
On 24/07/17 11:43 AM, Stefan Bodewig wrote:
On 2017-07-24, Jaikiran Pai wrote:
Ivy currently uses commons-httpclient for dealing with HTTP
repositories. This
On 2017-07-24, Jaikiran Pai wrote:
> Ivy currently uses commons-httpclient for dealing with HTTP
> repositories. This is an internal implementation detail of Ivy. The
> way it's implemented, it allows the user to use a version of their
> choice, of this library, by placing them in the runtime clas
omeone else).
Jan
-Ursprüngliche Nachricht-
Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
Gesendet: Montag, 24. Juli 2017 07:25
An: dev@ant.apache.org
Betreff: Ivy - No more support for commons-httpclient 2.x in runtime
classpath?
Ivy currently uses commons-httpclient for dealing with
-
> > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Montag, 24. Juli 2017 07:25
> > An: dev@ant.apache.org
> > Betreff: Ivy - No more support for commons-httpclient 2.x in runtime
> > classpath?
> >
> > Ivy currently uses commons-httpclien
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 24. Juli 2017 07:25
> An: dev@ant.apache.org
> Betreff: Ivy - No more support for commons-httpclient 2.x in runtime
> classpath?
>
> Ivy currently uses commons-httpc
Ivy currently uses commons-httpclient for dealing with HTTP
repositories. This is an internal implementation detail of Ivy. The way
it's implemented, it allows the user to use a version of their choice,
of this library, by placing them in the runtime classpath (similar to
some other libraries w
