You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Carsten Reckord (JIRA)" <ji...@apache.org> on 2017/04/04 08:46:41 UTC
[jira] [Closed] (HTTPCLIENT-1837) HttpClient-Win: Move
WinHttpClients to subpackage
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Reckord closed HTTPCLIENT-1837.
---------------------------------------
Looking good to me. Thank you very much.
> HttpClient-Win: Move WinHttpClients to subpackage
> -------------------------------------------------
>
> Key: HTTPCLIENT-1837
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1837
> Project: HttpComponents HttpClient
> Issue Type: Wish
> Components: HttpClient (classic)
> Affects Versions: 4.5.3
> Environment: HttpClient 4.5.3
> HttpClient-Win 4.5.3
> Reporter: Carsten Reckord
> Priority: Minor
> Fix For: 4.6 Alpha1
>
>
> 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