Re: HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-25 Thread Michael Osipov
Am 2015-11-25 um 21:07 schrieb Gary Gregory: [..] |- httpcore |- httpcore-ab |- httpcore-osgi We should always keep in mind that the artifact should be recognizable by its filname or id. Maybe httpcomponents-httpcore, -httpcore-ab, etc. would be better but they are, of course, longer. (imho)

Re: HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-25 Thread Gary Gregory
On Wed, Nov 25, 2015 at 12:03 PM, Michael Osipov wrote: > Am 2015-11-25 um 17:36 schrieb Oleg Kalnichevski: > >> Folks >> >> I made the first pass at re-arranging packages in HttpCore trunk and >> think it is presently good enough for 5.0-alpha1 >> >> Please feel free to take a look. >> > > Just

Re: HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-25 Thread Michael Osipov
Am 2015-11-25 um 17:36 schrieb Oleg Kalnichevski: Folks I made the first pass at re-arranging packages in HttpCore trunk and think it is presently good enough for 5.0-alpha1 Please feel free to take a look. Just checked. Looks like a tremendous move action. I will require a day or two to hav

HC 5.0: artifact id; Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-25 Thread Oleg Kalnichevski
Folks I made the first pass at re-arranging packages in HttpCore trunk and think it is presently good enough for 5.0-alpha1 Please feel free to take a look. I am now going to change artifact id from org.apache.httpcomponents:httpcore to org.apache.httpcomponents.core5:httpcore Please let me

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-24 Thread sebb
On 23 November 2015 at 09:46, Michael Osipov <1983-01...@gmx.net> wrote: >> On Mon, 2015-11-23 at 10:08 +0100, Michael Osipov wrote: >> > > On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: >> > > >> > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov >> > > > wrote: >> > > > >> > > > > Am 2015

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Michael Osipov
> On Mon, 2015-11-23 at 10:51 +0100, Michael Osipov wrote: > > > On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > > > > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > > > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > > > > >> Am 2015-11-21 um 18:01 schrieb Oleg Kalni

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Oleg Kalnichevski
On Mon, 2015-11-23 at 10:51 +0100, Michael Osipov wrote: > > On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > > > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > > > >> Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: >

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Michael Osipov
> On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > > >> Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: > > >>> Folks > > >>> > > >>> I moved code to org.apache.hc.core5

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Michael Osipov
> On Mon, 2015-11-23 at 10:08 +0100, Michael Osipov wrote: > > > On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: > > > > > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov > > > > wrote: > > > > > > > > > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > > > > > > > > > >> +1. > > > > >> > > >

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Oleg Kalnichevski
On Mon, 2015-11-23 at 10:08 +0100, Michael Osipov wrote: > > On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: > > > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov > > > wrote: > > > > > > > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > > > > > > > >> +1. > > > >> > > > >> I would not mind

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Oleg Kalnichevski
On Sun, 2015-11-22 at 20:42 +0100, Michael Osipov wrote: > Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: > > On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > >> Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: > >>> Folks > >>> > >>> I moved code to org.apache.hc.core5 namespace as t

Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-23 Thread Michael Osipov
> On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov > > wrote: > > > > > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > > > > > >> +1. > > >> > > >> I would not mind using Java 8 too. > > >> > > > > > > Believe that is too early. We are using

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-22 Thread Gary Gregory
On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov > wrote: > > > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > > > >> +1. > >> > >> I would not mind using Java 8 too. > >> > > > > Believe that is too early. We are using a company-wide, Eclipse R

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-22 Thread Jon Moore
On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov wrote: > Am 2015-11-21 um 19:52 schrieb Gary Gregory: > >> +1. >> >> I would not mind using Java 8 too. >> > > Believe that is too early. We are using a company-wide, Eclipse RCP-based > product which is on Eclipse 3.4/3.6 and still HttpClient 3.x.

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-22 Thread Michael Osipov
Am 2015-11-22 um 20:11 schrieb Oleg Kalnichevski: On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: Folks I moved code to org.apache.hc.core5 namespace as the first step. Now I would like to move things around in order to make the packa

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-22 Thread Oleg Kalnichevski
On Sat, 2015-11-21 at 19:48 +0100, Michael Osipov wrote: > Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: > > Folks > > > > I moved code to org.apache.hc.core5 namespace as the first step. > > > > Now I would like to move things around in order to make the package > > structure more consistent,

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-21 Thread Michael Osipov
Am 2015-11-21 um 19:52 schrieb Gary Gregory: +1. I would not mind using Java 8 too. Believe that is too early. We are using a company-wide, Eclipse RCP-based product which is on Eclipse 3.4/3.6 and still HttpClient 3.x. I highly doubt that the dev team will jump on e4 and Java 8 features. J

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-21 Thread Gary Gregory
+1. I would not mind using Java 8 too. Gary On Nov 21, 2015 9:03 AM, "Oleg Kalnichevski" wrote: > Folks > > I moved code to org.apache.hc.core5 namespace as the first step. > > Now I would like to move things around in order to make the package > structure more consistent, reduce circular depen

Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-21 Thread Michael Osipov
Am 2015-11-21 um 18:01 schrieb Oleg Kalnichevski: Folks I moved code to org.apache.hc.core5 namespace as the first step. Now I would like to move things around in order to make the package structure more consistent, reduce circular dependencies between packages and prepare for messaging code se

HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

2015-11-21 Thread Oleg Kalnichevski
Folks I moved code to org.apache.hc.core5 namespace as the first step. Now I would like to move things around in order to make the package structure more consistent, reduce circular dependencies between packages and prepare for messaging code separation into HTTP/1.1 and HTTP/2 compliant impleme