On 10/18/2014 05:36 PM, Oleg Kalnichevski wrote:
Vote: HttpComponents Core 4.3.3 release
[X] +1 Release the packages as HttpComponents Core 4.3.3.
[ ] -1 I am against releasing the packages (must include a reason).
asankha
--
Asankha C. Perera
Founder and CTO, AdroitLogic,
+1
...ant
On Sat, Oct 18, 2014 at 1:06 PM, Oleg Kalnichevski ol...@apache.org wrote:
Please vote on releasing these packages as HttpComponents Core 4.3.3.
The vote is open for the at least 72 hours, and only votes from
HttpComponents PMC members are binding. The vote passes if at least
Peter Binney created HTTPCLIENT-1573:
Summary: How do I get NTLM to use current users credentials/token?
Key: HTTPCLIENT-1573
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1573
Project:
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Binney updated HTTPCLIENT-1573:
-
Summary: How do I get NTLM to use current user credentials/token? (was:
How do I
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1573.
---
Resolution: Invalid
@Peter
See
Will we remove deprecated APIs in 5.0?
Gary
-- Forwarded message --
From: ol...@apache.org
Date: Tue, Oct 21, 2014 at 7:58 AM
Subject: svn commit: r1633350 - in /httpcomponents/httpcore/trunk:
httpcore-ab/pom.xml httpcore-nio/pom.xml httpcore-osgi/pom.xml
httpcore/pom.xml pom.xml
Folks
HttpCore trunk is now 5.0-alpha1. The main focus of 5.0 is compliance
with RFC 7230 and related RFCs. However this is a point when we can
revisit design decisions, re-do things that need to be re-done and
improve things that need to be improved without constraints of API
compatibility.
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178329#comment-14178329
]
Peter Binney commented on HTTPCLIENT-1573:
--
That's working a treat - many
On Tue, 2014-10-21 at 08:11 -0400, Gary Gregory wrote:
Will we remove deprecated APIs in 5.0?
Gary
For sure.
Oleg
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail:
On Tue, Oct 21, 2014 at 8:15 AM, Oleg Kalnichevski ol...@apache.org wrote:
On Tue, 2014-10-21 at 08:11 -0400, Gary Gregory wrote:
Will we remove deprecated APIs in 5.0?
Gary
For sure.
Then we need to rename the top-level package and Maven coordinates.
This what we did in Commons for
Hi Oleg,
Will there be a 4.x release that will deal with RFC 7230?
I am wondering why you propose breaking backwards compatibility at the same
time you propose adding major new functionality. I've looked at the RFC
and don't offhand see any reason why this should be related. We've just
gone
On Tue, 2014-10-21 at 08:47 -0400, Gary Gregory wrote:
On Tue, Oct 21, 2014 at 8:15 AM, Oleg Kalnichevski ol...@apache.org wrote:
On Tue, 2014-10-21 at 08:11 -0400, Gary Gregory wrote:
Will we remove deprecated APIs in 5.0?
Gary
For sure.
Then we need to rename the
On Tue, 2014-10-21 at 08:51 -0400, Karl Wright wrote:
Hi Oleg,
Will there be a 4.x release that will deal with RFC 7230?
I am wondering why you propose breaking backwards compatibility at the same
time you propose adding major new functionality.
I think it was proposed more than three
On Tue, Oct 21, 2014 at 8:14 AM, Oleg Kalnichevski ol...@apache.org wrote:
Folks
HttpCore trunk is now 5.0-alpha1. The main focus of 5.0 is compliance
with RFC 7230 and related RFCs. However this is a point when we can
revisit design decisions, re-do things that need to be re-done and
bq. I think it was proposed more than three months ago.
Well, three months ago I was in the midst of a major release cycle, so I'm
not surprised I missed it go by.
bq. If RFC 7230 related changes turn out to be minor there is nothing that
stops us from porting them to 4.4. But I doubt it is
On Tue, 2014-10-21 at 09:49 -0400, Gary Gregory wrote:
On Tue, Oct 21, 2014 at 8:14 AM, Oleg Kalnichevski ol...@apache.org wrote:
Folks
HttpCore trunk is now 5.0-alpha1. The main focus of 5.0 is compliance
with RFC 7230 and related RFCs. However this is a point when we can
revisit
On Tue, 2014-10-21 at 09:56 -0400, Karl Wright wrote:
bq. I think it was proposed more than three months ago.
Well, three months ago I was in the midst of a major release cycle, so I'm
not surprised I missed it go by.
bq. If RFC 7230 related changes turn out to be minor there is nothing
The vote to release HttpComponents Core 4.3.3 based on RC1 has passed
with the following results
+1 (4 binding votes in total)
Gary Gregory ggregory -at- apache.org *
Oleg Kalnichevski olegk -at- apache.org *
Asankha C. Perera asankha -at- apache.org *
ant elder antelder -at- apache.org *
no
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38715projectId=302
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 21 Oct 2014 20:01:19 +
Finished at: Tue 21 Oct 2014 20:01:21 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38717projectId=304
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 21 Oct 2014 20:01:30 +
Finished at: Tue 21 Oct 2014 20:01:33 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38718projectId=305
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 21 Oct 2014 20:01:34 +
Finished at: Tue 21 Oct 2014 20:01:37 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38719projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 21 Oct 2014 21:01:17 +
Finished at: Tue 21 Oct 2014 21:01:19 +
Total time: 1s
Build Trigger: Schedule
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179118#comment-14179118
]
Michael Osipov commented on HTTPCLIENT-1573:
[~PeterBinney], my
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38720projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 21 Oct 2014 22:01:19 +
Finished at: Tue 21 Oct 2014 22:01:21 +
Total time: 1s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38721projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 21 Oct 2014 23:01:21 +
Finished at: Tue 21 Oct 2014 23:01:24 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38723projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 22 Oct 2014 01:01:20 +
Finished at: Wed 22 Oct 2014 01:01:22 +
Total time: 1s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38724projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 22 Oct 2014 02:01:46 +
Finished at: Wed 22 Oct 2014 02:01:48 +
Total time: 1s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38725projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 22 Oct 2014 03:01:22 +
Finished at: Wed 22 Oct 2014 03:01:24 +
Total time: 1s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38726projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 22 Oct 2014 04:01:20 +
Finished at: Wed 22 Oct 2014 04:01:22 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38728projectId=303
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 22 Oct 2014 05:01:21 +
Finished at: Wed 22 Oct 2014 05:01:23 +
Total time: 1s
Build Trigger: Schedule
How about bumping to Java 7?
Gary
On Tue, Oct 21, 2014 at 8:14 AM, Oleg Kalnichevski ol...@apache.org wrote:
Folks
HttpCore trunk is now 5.0-alpha1. The main focus of 5.0 is compliance
with RFC 7230 and related RFCs. However this is a point when we can
revisit design decisions, re-do
31 matches
Mail list logo
