hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Reckord (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPCLIENT-1837) HttpClient-Win: Move WinHttpClients to subpackage
Date Mon, 03 Apr 2017 11:48:41 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Reckord updated HTTPCLIENT-1837:
----------------------------------------
    Description: 
Please move org.apache.http.impl.client.WinHttpClients to a separate package (e.g. org.apache.http.impl.client.win.WinHttpClients).

HttpClient-Win 5.0alpha already moves all code to a unique package of its own. It would be
great to do something similar for the WinHttpClients class in 4.5.x releases. 

Background: I'm trying to consume HttpClient-Win in an OSGi environment by converting it into
an OSGi bundle. This is made difficult because it exposes the same package org.apache.http.impl.client
as the main HttpClient, which is problematic in OSGi, especially since users will often want
to consume both packages.

It should be fine to just deprecate the old class in favor of the moved one - this gives us
the opportunity in OSGi to simply consume the new package and ignore the old one (or even
not export it).

  was:
Please move org.apache.http.impl.client.WinHttpClients to a separate package (e.g. org.apache.http.impl.client.win.WinHttpClients).

HttpClient-Win 5.0alpha already moves all code to a unique package of its own. It would be
great to do the same in 4.5.x releases. 

Background: I'm trying to consume HttpClient-Win in an OSGi environment by converting it into
an OSGi bundle. This is made difficult because it exposes the same package org.apache.http.impl.client
as the main HttpClient, which is problematic in OSGi, especially since users will often want
to consume both packages.

It should be fine to just deprecate the old class in favor of the moved one - this gives us
the opportunity in OSGi to simply consume the new package and ignore the old one (or even
not export it).


> HttpClient-Win: Move WinHttpClients to subpackage
> -------------------------------------------------
>
>                 Key: HTTPCLIENT-1837
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1837
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.3
>         Environment: HttpClient 4.5.3
> HttpClient-Win 4.5.3
>            Reporter: Carsten Reckord
>
> Please move org.apache.http.impl.client.WinHttpClients to a separate package (e.g. org.apache.http.impl.client.win.WinHttpClients).
> HttpClient-Win 5.0alpha already moves all code to a unique package of its own. It would
be great to do something similar for the WinHttpClients class in 4.5.x releases. 
> Background: I'm trying to consume HttpClient-Win in an OSGi environment by converting
it into an OSGi bundle. This is made difficult because it exposes the same package org.apache.http.impl.client
as the main HttpClient, which is problematic in OSGi, especially since users will often want
to consume both packages.
> It should be fine to just deprecate the old class in favor of the moved one - this gives
us the opportunity in OSGi to simply consume the new package and ignore the old one (or even
not export it).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message