Am 2017-05-04 um 16:51 schrieb Oleg Kalnichevski:
On Thu, 2017-05-04 at 15:59 +0200, Michael Osipov wrote:
While I do say +1 the vote is incomplete:
You missed to provide the target Git repo names. E.g., you won't name
httpcomponents/project/ => project right?
Does this need to b
Am 2017-05-05 um 02:02 schrieb Gary Gregory:
Hi,
In Core 4.4.x we have:
SSLContextBuilder.useProtocol(String)
and in 5.0, we have:
SSLContextBuilder.setProtocol(String)
How about adding SSLContextBuilder.setProtocol(String) to 4.4.x and
deprecating useProtocol(String) to make porting easier?
> On Mon, 2017-05-08 at 09:41 +0200, Oleg Kalnichevski wrote:
> > The vote to migrate active HttpComponents projects from SVN
> > repository
> > to a Git repository has passed with the following results
> >
> > +1
> >
> > Oleg Kalnichevski
> On Mon, 2017-05-08 at 11:48 +0200, Michael Osipov wrote:
> > Based on Daniel Gruno's answer, we should discuss repo names first.
> >
> > Michael
> >
>
> OK. How about this?
>
> HttpCore -> httpcomponents-core
> HttpClient -> http
Am 2017-05-08 um 19:59 schrieb Gary Gregory:
Hi All,
We recently had a request to support Google's Brotli decompression
algorithm.
We decided NOT to add a dependency on the Brotli jar and I suggested that
the patch be provided against Apache Commons Compress, which was kindly
done and will be p
Am 2017-05-08 um 15:51 schrieb Oleg Kalnichevski:
On Mon, 2017-05-08 at 14:54 +0200, Oleg Kalnichevski wrote:
On Mon, 2017-05-08 at 14:12 +0200, Michael Osipov wrote:
On Mon, 2017-05-08 at 11:48 +0200, Michael Osipov wrote:
Based on Daniel Gruno's answer, we should discuss repo names
Am 2017-05-08 um 20:59 schrieb Oleg Kalnichevski:
On Mon, 2017-05-08 at 20:34 +0200, Michael Osipov wrote:
...
This was intentional. I would also like to use that repository to
contain style check definitions and possibly other project global
things.
Can you live with it being
Please do not forget to rename trunk to master:
https://git-wip-us.apache.org/repos/asf?p=httpcomponents-core.git;a=shortlog;h=refs/heads/trunk
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-ma
Am 2017-05-10 um 09:59 schrieb Oleg Kalnichevski:
I collected all your latest SVN commits and pushed them to the Git
repo. Nothing should have been lost.
One personal request. Do you think you could try to make your commits
less granular and combine logically related changes into larger change
Hi folks,
given that Oleg finally took up the chance migrating core and client to
a Git-based repo, we should agree how we are going to work with in
conformance with a good Git practice to avoid chaos on master. I'd like
to provide an example first why a common practive is so necessary to
mak
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski
wrote:
...
One personal request. Do you think you could try to make your
commits
less granular and combine logically related change
Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski
wrote:
...
One
Am 2017-05-10 um 21:22 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:06 +0200, Michael Osipov wrote:
Hi folks,
given that Oleg finally took up the chance migrating core and client
to
a Git-based repo, we should agree how we are going to work with in
conformance with a good Git practice
Am 2017-05-10 um 21:31 schrieb Bindul Bhowmik:
On Wed, May 10, 2017 at 1:25 PM, sebb wrote:
It would be helpful to document this on the Wiki and/or website
On 10 May 2017 at 20:22, Oleg Kalnichevski wrote:
On Wed, 2017-05-10 at 21:06 +0200, Michael Osipov wrote:
Hi folks,
given that Oleg
Folks,
since there is still some disagreement on how an issue should be applied
to 4.4.x and 5.0.x, I'd like to propose the following two ideas:
Have one repo per major version and all pain will end:
httpcomponents-core-4
httpcomponents-client-4
httpcomponents-core-5
httpcomponents-client-5
Am 2017-05-10 um 21:42 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:27 +0200, Michael Osipov wrote:
Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15
Am 2017-05-10 um 21:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:36 +0200, Michael Osipov wrote:
...
I would still ask for master being mutable (rewritable) or abandon
the
concept of a master branch as inapplicable in favor of a release
branch
such as 5.0.x.
One master per
Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
This will a problem anyway because all paths change (package names,
etc.). Hopefully Git's similarity algorithm can detect this.
No, it is not. Git is that great. It always amaz
Am 2017-05-10 um 23:19 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 22:00 +0200, Michael Osipov wrote:
Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
This will a problem anyway because all paths change (package
names,
etc
Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote:
...
But your answer is contrary to your previous statement -- cherry-
picking
shouldn't be a fuzz with two different repos. Can you explain
why?
My understanding is that c
d "Git policies
and practices". I don't want either the master/release branch to be
rewritten.
On Thu, May 11, 2017 at 9:23 AM, Oleg Kalnichevski wrote:
On Thu, 2017-05-11 at 00:00 +0200, Michael Osipov wrote:
Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski:
On Wed, 2017
Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
Force pushing is considered a bad practice in Git for good reasons,
thus rewriting history of published branches is IMHO a no-go. It
makes
everybody's life harder (and developers less exper
Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 14:58 +0200, Michael Osipov wrote:
Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
Force pushing is considered a bad practice in Git for good
reasons,
thus
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 15:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski:
I have _no_ intention of policing other committers. It is
emotionally
cheaper for me to take time to clean things up and than
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
What benefit do you have if it is hard to follow the code paths? How
much is "good" code worth if you don
Am 2017-05-15 um 17:19 schrieb Gary Gregory:
On Mon, May 15, 2017 at 8:04 AM, Michael Osipov wrote:
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
What benefit do you
Am 2017-05-15 um 17:19 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 17:04 +0200, Michael Osipov wrote:
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
I actually did:
https://mail-archives.apache.org/mod_mbox/hc-dev
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1. Branch off master ({{{git checkout -b / master}}})
where {{{}}} is the branch you are going to apply the fix, e
Am 2017-05-15 um 18:34 schrieb Gary Gregory:
Hi,
Thank you for kicking off this thread.
I do not think "/" is good enough. At least when I tried
it, EGit would not let me create a branch in a branch which makes sense.
Which is what I used dev/4.4.x/HTTPCORE-466 in the HttpCore Git repo.
This
Am 2017-05-15 um 18:43 schrieb Gary Gregory:
Altassian has a plugin to handle (7) IIRC, we use something like that at
work but for SVN. The plugin links a JIRA ticket to commits if the commit
message includes the string [JIRA-ID]. There is also Altassian FishEye.
I aware of that plugin. In fact
Am 2017-05-15 um 18:59 schrieb Michael Osipov:
Am 2017-05-15 um 18:43 schrieb Gary Gregory:
Altassian has a plugin to handle (7) IIRC, we use something like that at
work but for SVN. The plugin links a JIRA ticket to commits if the commit
message includes the string [JIRA-ID]. There is also
l never be able to define the
duration of temp, one day, week, months? The dev/ seems redundant to
because 4.4.x -- note the X implies development on a bugfix branch.
Michael
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put i
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1. Branch
Am 2017-05-15 um 20:18 schrieb Gary Gregory:
On Mon, May 15, 2017 at 11:13 AM, Michael Osipov
wrote:
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov
wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https
Am 2017-05-15 um 20:22 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 20:13 +0200, Michael Osipov wrote:
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov
...
Which of the paths should we pick:
https://makandracards.com/makandra/527-squash
Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1
Am 2017-05-15 um 20:43 schrieb Gary Gregory:
On Mon, May 15, 2017 at 11:37 AM, Michael Osipov
wrote:
Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki
Am 2017-05-16 um 09:22 schrieb Oleg Kalnichevski:
So, I woke up this morning, took a look at my mail box and found two
wonderful commit messages on top of the 4.4.x release branch saying
'oh, forgot this' and 'ah, forgot that' immediately after a dev branch
merge.
Shit like that will happen over
Hi Julian,
Am 2017-05-17 um 09:30 schrieb Julian Sedding:
Hi Oleg and Michael
I understand your frustration with a messy commit log.
Personally I strive to give context so that the commit can more easily
be understood. Normally that includes a JIRA ID and the title. There
are cases where I pre
Am 2017-05-18 um 09:31 schrieb Oleg Kalnichevski:
On Wed, 2017-05-17 at 09:12 -0700, Gary Gregory wrote:
On May 17, 2017 6:54 AM, "Oleg Kalnichevski"
wrote:
Folks
HttpCore / HttpClient have been fully migrated to Git, GitHub
replication and all.
Happy hacking, pushing and rebasing.
We now n
Am 2017-05-18 um 09:38 schrieb Oleg Kalnichevski:
On Wed, 2017-05-17 at 22:56 -0700, Gary Gregory wrote:
Now that I am done with the branch dev/4.4.x/HTTPCORE-468 and the
code is
merged into 4.4.x, is it OK to delete the branch?
Of course, once merged a dev branch should be deleted in the rem
Since I haven't received anymore comments on the guidelines, I'll close
the questioning and call a vote for commmitters and PMC members.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e
Hi folks,
I am casting this vote for the previously discussed Git guidelines for
all committers to make life easier for everyone. If the vote passes,
every committer must abide to this.
The guidelines:
= Typical Issue Workflow =
1. Branch off a release branch (e.g., 4.4.x, 5.0.x) ({{{git ch
Am 2017-05-21 um 11:42 schrieb Oleg Kalnichevski:
On Sun, 2017-05-21 at 08:52 +, Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on
"Httpcomponents Wiki" for change notification.
The "GitGuidelines" page has been changed by MichaelOsipov:
https://wiki
Am 2017-05-21 um 19:07 schrieb Oleg Kalnichevski:
On Sun, 2017-05-21 at 17:27 +0200, Michael Osipov wrote:
...
Am 2017-05-21 um 11:42 schrieb Oleg Kalnichevski:
What is a timeframe you consider rewriting if necessary? A week?
Three
days? The shorter the timeframe the less likely it is
if there a bug fix I just must have ASAP.
On what do you exact Git steps? How to squash/rewrite? On a release?
Maven Release Plugin does that for you
On May 21, 2017 2:00 AM, "Michael Osipov" wrote:
Hi folks,
I am casting this vote for the previously discussed Git guidelines for al
Am 2017-05-22 um 09:59 schrieb Oleg Kalnichevski:
On Sun, 2017-05-21 at 21:17 +0200, Michael Osipov wrote:
Am 2017-05-21 um 19:07 schrieb Oleg Kalnichevski:
On Sun, 2017-05-21 at 17:27 +0200, Michael Osipov wrote:
...
Am 2017-05-21 um 11:42 schrieb Oleg Kalnichevski:
What is a timeframe
Am 2017-05-22 um 20:29 schrieb Gary Gregory:
On Mon, May 22, 2017 at 11:16 AM, Michael Osipov
wrote:
Am 2017-05-22 um 06:46 schrieb Gary Gregory:
I will follow whatever the community decides; my only request is that
precise git instructions be provided for contributors and RMs. I'm
> Hi Oleg,
>
> I'm sure we need no noise at all but I could not figure out how to clean it
> up.
>
> I do know that got one cherry-picked commit right for one of the tickets.
>
> For the other, I could not get rid of the merge commits.
If you can't merge properly, please ask for help before m
Am 2017-05-24 um 13:49 schrieb Oleg Kalnichevski:
On Wed, 2017-05-24 at 11:51 +0200, Michael Osipov wrote:
Hi Oleg,
I'm sure we need no noise at all but I could not figure out how to
clean it
up.
I do know that got one cherry-picked commit right for one of the
tickets.
For the other, I
Am 2017-05-21 um 11:00 schrieb Michael Osipov:
Vote is open until 2017-05-25 00:00 Etc/UTC.
I am extending the vote until 2017-05-27 00:00 Etc/UTC due to low activity.
[ ] +1 Committers must abide to these Git guidelines while working on
the code
[ ] -1 I do not agree with this guideline
if there a bug fix I just must have ASAP.
Do you intend to abstain from your vote? Or is this an indirect +1?
Michael
On May 21, 2017 2:00 AM, "Michael Osipov" wrote:
Hi folks,
I am casting this vote for the previously discussed Git guidelines for all
committers to make life easier
Am 2017-05-21 um 11:00 schrieb Michael Osipov:
Hi folks,
I am casting this vote for the previously discussed Git guidelines for
all committers to make life easier for everyone. If the vote passes,
every committer must abide to this.
The guidelines:
= Typical Issue Workflow =
1. Branch off a
Am 2017-05-24 um 18:55 schrieb Oleg Kalnichevski:
.
Michael,
Is there anything holding back the vote?
Not from my side. I did cast it (see [VOTE] Git Guidelines), but didn't
receive no official votes. I will extend the period.
Don't forget to cast your vote!
Michael
The subject of the v
Hi folks,
I am re-casting this vote for the previously discussed Git guidelines
for all committers to make life easier for everyone. If the vote passes,
every committer must abide to this.
The guidelines:
= Typical Issue Workflow =
1. Branch off a release branch (e.g., 4.4.x, 5.0.x) ({{{git
Am 2017-05-24 um 19:11 schrieb Michael Osipov:
Hi folks,
I am re-casting this vote for the previously discussed Git guidelines
for all committers to make life easier for everyone. If the vote passes,
every committer must abide to this.
The guidelines:
= Typical Issue Workflow =
1. Branch off
Am 2017-05-24 um 19:11 schrieb Michael Osipov:
Hi folks,
I am re-casting this vote for the previously discussed Git guidelines
for all committers to make life easier for everyone. If the vote passes,
every committer must abide to this.
The guidelines:
= Typical Issue Workflow =
1. Branch off
ure that this merge won't incur a merge commit
This is intentional. Oleg wanted it so as far as I remember. The reason
is also that simply do not follow a proper workflow, branch, work
squash, rebase, merge.
On Mon, May 29, 2017 at 9:51 PM, Michael Osipov wrote:
Am 2017-05-24 um
points?
We can rename it to Git Rules if you want, so this will be mandatory for
all committers. Btw, you recommended to rename to Git Guidelines...
Michael
On Mon, May 29, 2017 at 9:51 PM, Michael Osipov
wrote:
Am 2017-05-24 um 19:11 schrieb Michael Osipov:
Hi folks,
I am re-casting this vo
Am 2017-12-01 um 10:09 schrieb Oleg Kalnichevski:
Folks
It is going to be unpleasant but we need to revisit a highly
contentious issue of the choice of a logging APIs for HttpClient 5.0.
I personally like Log4J2 and generally am a satisfied user of the
toolkit. However, Log4J2 logging facade AP
you point me to the discussion? I will have a look at it.
Michael
Oleg
On Jan 10, 2018 01:54, "Oleg Kalnichevski" wrote:
On Mon, 2018-01-08 at 11:45 +0100, Oleg Kalnichevski wrote:
On Fri, 2017-12-08 at 22:14 +0100, Michael Osipov wrote:
Am 2017-12-01 um 10:09 schrieb Oleg Ka
Am 2018-01-13 um 11:50 schrieb Oleg Kalnichevski:
On January 13, 2018 11:26:01 AM GMT+01:00, Michael Osipov
wrote:
Am 2018-01-10 um 15:12 schrieb Oleg Kalnichevski:
On Wed, 2018-01-10 at 06:53 -0700, Gary Gregory wrote:
I am a disappointed but I understand.
Gary
Michael
Will this
Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski:
Folks
We have a dubious honor of having absolutely the most hideous project
web site in existence. It makes my eyes bleed every time I have to
update it. It is simply horrible.
I would like to migrate project website sources from Maven apt and x
Am 2018-02-03 um 10:31 schrieb Oleg Kalnichevski:
On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote:
Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski:
Folks
We have a dubious honor of having absolutely the most hideous
project
web site in existence. It makes my eyes bleed every time I
Am 2018-02-06 um 19:39 schrieb Oleg Kalnichevski:
On Tue, 2018-02-06 at 16:45 +, sebb wrote:
On 6 February 2018 at 14:31, Oleg Kalnichevski
...
...
I *am* saying we need to preserve links.
Moving from Maven may make this harder, so that needs to be
factored
in to the decision.
So,
Am 2018-02-25 um 17:38 schrieb Gary Gregory:
My selfish POV is Java 8 and a longer beta cycle. I am not able to migrate
to HC 5 ATM for my proxy product due to the usual busy. So I'd like HC 5 to
be as modern as possible by the time I get to it.
This is actually a personal problem, not one of t
Hi folks,
I have been recently promoted as HC committer by Oleg. Being an Apache
committer for serveral years now, contributing to Apache Maven, I
finally decided to join this project too.
Oleg asked me to join to make improvements on the GSS-API-based and
SSPI-based (Windows) authentication
Hi Karl and thanks for the welcome,
Am 2014-11-14 um 17:44 schrieb Karl Wright:
Welcome onboard!
I'm the lead with the ManifoldCF project, which is a heavy user of
httpclient, and the implementer of the NTLM code that HttpClient currently
includes. I'm looking forward to someone keeping up to
ter.
On Fri, Nov 14, 2014 at 12:47 PM, Michael Osipov
wrote:
Hi Karl and thanks for the welcome,
Am 2014-11-14 um 17:44 schrieb Karl Wright:
Welcome onboard!
I'm the lead with the ManifoldCF project, which is a heavy user of
httpclient, and the implementer of the NTLM code that HttpC
it is the only one that has anyone on it, but I am not sure if
that is only for PMC members or both PMCs and Committers...
Gary
On Fri, Nov 14, 2014 at 11:36 AM, Michael Osipov
wrote:
Hi folks,
I have been recently promoted as HC committer by Oleg. Being an Apache
committer for serveral
se of GSSCredential
and always assumes implicit credential. Fortunately, there are several
ways to solve that problem too.
Michael
On Fri, Nov 14, 2014 at 1:06 PM, Michael Osipov wrote:
Am 2014-11-14 um 18:53 schrieb Karl Wright:
Hi Michael,
[...]
Native code is not something that will wor
sourceforge.net/xref/net/sf/michaelo/dirctxsrc/DirContextSource.html#L510
[2]
http://tomcatspnegoad.sourceforge.net/xref/net/sf/michaelo/tomcat/authenticator/CurrentWindowsIdentityAuthenticator.html#L93
Michael
On Fri, Nov 14, 2014 at 1:38 PM, Michael Osipov wrote:
Am 2014-11-14 um 19:21 schr
rstand its logic.
Michael
On Fri, Nov 14, 2014 at 2:36 PM, Michael Osipov wrote:
Am 2014-11-14 um 20:00 schrieb Karl Wright:
bq. Unfortunately, HTTPClient does not support direct use of GSSCredential
and always assumes implicit credential. Fortunately, there are several
ways
to solve that p
Am 2014-11-16 um 13:08 schrieb Oleg Kalnichevski:
On Sat, 2014-11-15 at 21:58 +0100, Michael Osipov wrote:
Am 2014-11-15 um 14:27 schrieb Karl Wright:
Hi Michael,
I understand how the workaround would work if I should implement it that
way, but I'm less certain about your proposed chang
Am 2014-12-01 um 11:46 schrieb Oleg Kalnichevski:
Folks
There has been no bug reports / change requests for the 4.4 branch of
HttpCore for some while. I see no good reasons to delay 4.4 GA release
any longer given that new development efforts have moved to trunk (5.0).
Are there any objections
Am 2015-01-19 um 17:38 schrieb Oleg Kalnichevski:
Folks
Please review 4.4 release notes and make changes / amendments you
deem necessary:
http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/RELEASE_NOTES.txt
@Michael,
I hope the statement about experimental status of the Native W
Am 2015-01-19 um 22:22 schrieb Oleg Kalnichevski:
On Mon, 2015-01-19 at 20:56 +0100, Michael Osipov wrote:
Am 2015-01-19 um 17:38 schrieb Oleg Kalnichevski:
Folks
Please review 4.4 release notes and make changes / amendments you
deem necessary:
http://svn.apache.org/repos/asf/httpcomponents
Am 2015-02-08 um 00:41 schrieb Karl Wright:
Hi folks,
I saw the latest httpclient release go out the door. It was not clear,
though, whether Kerberos integration had been completed in the manner
planned, using the same credential setup other authentication methods
currently use. Can someone fi
Hi folks,
stupid questions: why do the release notes [1] not mention a word about
4.4 and why is the version in JIRA not released with an unresolved issue
[2]?
[1] http://www.apache.org/dist/httpcomponents/httpcore/RELEASE_NOTES.txt
[2]
https://issues.apache.org/jira/browse/HTTPCORE-369?jql=
Am 2015-02-11 um 09:33 schrieb Oleg Kalnichevski:
On Tue, 2015-02-10 at 22:25 +0100, Michael Osipov wrote:
Hi folks,
stupid questions: why do the release notes [1] not mention a word about
4.4
Because the trunk is 5.0. The 4.4.x branch can be found here
http://svn.apache.org/repos/asf
Am 2015-02-11 um 21:24 schrieb sebb:
On 11 February 2015 at 14:23, wrote:
Author: michaelo
Date: Wed Feb 11 14:23:29 2015
New Revision: 1658967
URL: http://svn.apache.org/r1658967
Log:
HTTPCORE-395: VersionInfo#getUserAgent reports incorrect Java version
Modified:
httpcomponents/httpco
Am 2015-02-17 um 11:04 schrieb Oleg Kalnichevski:
Folks
It looks like the only proper way of resolving HTTPCLIENT-1613 [1] is to
extend existing APIs, which (at least ideally) should require a new
feature release and a full ALPHA / BETA development cycle.
We, of course, could just cut 4.5 GA ri
Am 2015-02-17 um 11:04 schrieb Oleg Kalnichevski:
Folks
It looks like the only proper way of resolving HTTPCLIENT-1613 [1] is to
extend existing APIs, which (at least ideally) should require a new
feature release and a full ALPHA / BETA development cycle.
We, of course, could just cut 4.5 GA ri
Am 2018-03-30 um 18:51 schrieb Gary Gregory:
Hi All:
Right now, the HttpClient is of the form:
User-Agent: Apache-HttpClient/4.5.5 (Java/1.8.0_162)
With the stack I am working with, it would be handy if the header reflected:
This is your personal problem, not the client ones.
- The Java
Am 2018-04-06 um 18:02 schrieb Gary Gregory:
Hi All:
I have cases where I want to use a Set of org.apache.http.NameValuePair
instead of a list of NameValuePair (to track what headers I need to remove
for example.).
But, since NameValuePair does not specify equals() and hashCode() it feels
like
Am 2018-04-06 um 18:19 schrieb Oleg Kalnichevski:
On Fri, 2018-04-06 at 10:02 -0600, Gary Gregory wrote:
Hi All:
I have cases where I want to use a Set of
org.apache.http.NameValuePair
instead of a list of NameValuePair (to track what headers I need to
remove
for example.).
But, since NameValu
Am 2018-08-06 um 19:31 schrieb Gary Gregory:
Hi All:
All constants in the HttpStatus class are prefixed with HC_.
Why bother?
IMO this:
if (code == HttpStatus.OK) {
}
reads better than:
if (code == HttpStatus.SC_OK) {
}
I don't have to think about what "SC" means, I already know that I am
Am 2018-08-13 um 17:31 schrieb Oleg Kalnichevski:
Folks
Do we want to continue supporting OSGi? We cannot do it properly, so we
might as well not do it at all.
Is it only about the MANIFEST.MF?
If we cannot reasonably maintain it because of lack of knowledge, it is
better then not to provide
Am 2018-09-30 um 20:57 schrieb Gary Gregory:
IMO, we should
rename org.apache.hc.core5.http.MessageHeaders.getAllHeaders() to
getHeaders(). The "All" is not needed IMO. We do not have "All" in other
API names, for example we have "headerIterator()" in the same class and not
"allHeadersIterator()"
Am 2018-10-01 um 16:33 schrieb Gary Gregory:
Also, since we are here, in the same place: "Header
getSingleHeader(String)", could be be "getHeader(String)"; since the
"Single" is implied by the singular "Header" in the API name _and_ by the
return type.
Thoughts on that one?
Makes sense to me.
Am 2018-10-02 um 19:55 schrieb Gary Gregory:
Here is another odd one:
org.apache.hc.core5.http.MessageHeaders.containsHeaders(String) : int
"contains" normally returns a boolean, but here the API _counts_ headers,
therefore I propose the name "countHeaders(String) : int".
Make sense here too.
Am 2018-10-03 um 16:55 schrieb Gary Gregory:
On Wed, Oct 3, 2018 at 7:17 AM Oleg Kalnichevski wrote:
On Tue, 2018-10-02 at 15:34 -0600, Gary Gregory wrote:
On Tue, Oct 2, 2018 at 2:09 PM Oleg Kalnichevski
wrote:
On October 2, 2018 9:57:40 PM GMT+02:00, Michael Osipov <
micha...@apache.
Am 2018-10-03 um 18:38 schrieb Gary Gregory:
On Wed, Oct 3, 2018 at 10:18 AM Michael Osipov wrote:
Am 2018-10-03 um 16:55 schrieb Gary Gregory:
On Wed, Oct 3, 2018 at 7:17 AM Oleg Kalnichevski
wrote:
On Tue, 2018-10-02 at 15:34 -0600, Gary Gregory wrote:
On Tue, Oct 2, 2018 at 2:09 PM
> Gesendet: Donnerstag, 04. Oktober 2018 um 16:25 Uhr
> Von: "Gary Gregory"
> An: "HttpComponents Project"
> Cc: "Michael Osipov"
> Betreff: Re: TimeoutMillis is horrible
>
> On Wed, Oct 3, 2018 at 2:15 PM Gary Gregory wrote:
>
Am 2018-10-04 um 17:38 schrieb Gary Gregory:
On Thu, Oct 4, 2018 at 9:29 AM Michael Osipov <1983-01...@gmx.net> wrote:
Gesendet: Donnerstag, 04. Oktober 2018 um 16:25 Uhr
Von: "Gary Gregory"
An: "HttpComponents Project"
Cc: "Michael Osipov"
Betreff: R
Am 2018-10-04 um 22:40 schrieb Gary Gregory:
On Thu, Oct 4, 2018 at 12:47 PM Michael Osipov wrote:
Am 2018-10-04 um 17:38 schrieb Gary Gregory:
On Thu, Oct 4, 2018 at 9:29 AM Michael Osipov <1983-01...@gmx.net>
wrote:
Gesendet: Donnerstag, 04. Oktober 2018 um 16:25 Uhr
Von: "G
I like it a lot too, but why are internal value retained as int/long and
not use the TimeValue clasS?
Am 2018-10-05 um 16:05 schrieb Gary Gregory:
Nice! :-)
Gary
-- Forwarded message -
From:
Date: Fri, Oct 5, 2018 at 2:24 AM
Subject: httpcomponents-core git commit: Use TimeVa
Am 2018-10-05 um 21:53 schrieb Gary Gregory:
Hi All:
Here is what I'd like to see in the near future.
- Release Commons Text 1.6 (I know we just released 1.5.)
- Integrate new string lookups and release Commons Configuration 2.4
Wrong list?
---
Am 2018-10-06 um 19:37 schrieb Oleg Kalnichevski:
On Sat, 2018-10-06 at 10:03 +0200, Michael Osipov wrote:
I like it a lot too, but why are internal value retained as int/long
and
not use the TimeValue clasS?
Should they be?
From a consistency point of view doesn't it make sense? Othe
Am 2018-10-06 um 21:15 schrieb Gary Gregory:
On Sat, Oct 6, 2018 at 12:57 PM Michael Osipov wrote:
Am 2018-10-06 um 19:37 schrieb Oleg Kalnichevski:
On Sat, 2018-10-06 at 10:03 +0200, Michael Osipov wrote:
I like it a lot too, but why are internal value retained as int/long
and
not use the
101 - 200 of 1413 matches
Mail list logo
