On 2015-10-07 3:13 PM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.28 release is now available for voting.
The main changes since 8.0.27 are:
- Allow file based configuration resources (e.g. key stores) to be
configured using URLs
- Restore code signing to the Windows installer an u
[X] Stable - go ahead and release as 8.0.27
-- Jeanfrancois
On 2015-09-28 7:26 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.27 release is now available for voting.
The main changes since 8.0.26 are:
- Correctly handle \${ vs \$ escaping in JSP and EL
- Fix for issues with NIO + SS
[X] Stable - go ahead and release as 8.0.26
Tested WebSocket and Async stuff using via Atmosphere test framework.
-- Jeanfrancois
On 2015-08-18 8:42 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.26 release is now available for voting.
This fixes the BOM issue with changelog.xml in the
On 2015-05-21 5:06 PM, Rémy Maucherat wrote:
2015-05-14 15:14 GMT+02:00 Mark Thomas :
Option 1: Tomcat 6.0.x EOL as of 30 June 2016
Option 2: Tomcat 6.0.x EOL as of 31 December 2016
It has been around for a very long time (2007) but it is a very significant
release, so option 2 is probably b
On 2015-05-19 2:43 PM, Mark Thomas wrote:
The proposed 8.0.23 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.23
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
The proposed 8.0.21 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.21
Tested websockets/AsyncContext with JDK7/8 and all major browsers.
-- Jeanfrancois
On 2015-03-23 10:59 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.21 release is now available for v
[X] Stable - go ahead and release as 8.0.18
Tested WebSockets & AsyncContext
-- Jeanfrancois
On 2015-01-23 8:09 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.18 release is now available for voting.
The main changes since 8.0.17 are:
- Fix a regression that resulted in truncated respon
On 2015-01-09 1:26 PM, Mark Thomas wrote:
The proposed 8.0.17 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.17
Tested WebSocket + AsyncContext
-- Jeanfrancois
-
To unsubscribe, e-mail:
On 2014-11-03, 4:51 AM, Mark Thomas wrote:
The proposed 8.0.15 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.14
Tested Websockets & AsyncContext API.
-- Jeanfrancois
-
To unsubscribe, e
On 2014-09-24, 5:07 PM, Mark Thomas wrote:
The proposed 8.0.14 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.14
Tested WebSockets and Servlet 3 AsyncContext API.
-- Jeanfrancois
-
To uns
On 2014-08-30, 11:34 AM, Mark Thomas wrote:
The proposed 8.0.12 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.0.12
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
Hi,
Note: (issue doesn't happens with blocking I/O, _only with
Http11NioProtocol_)
on some network, when Tomcat 7.0.50+ times a websocket connection, the
closeReason is set to 1006 but the websocket is not closed
automatically, as far as I can tell. So when an application try to
close, the
The proposed 8.0.9 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.9 (alpha)
[ ] Beta - go ahead and release as 8.0.9 (beta)
[X] Stable - go ahead and release as 8.0.9 (stable)
Websocket & Comet/Servlet 3.1 Async tested.
-- Jeanfrancois
--
On 2014-05-20, 6:04 AM, Violeta Georgieva wrote:
The proposed 7.0.54 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.54 Stable
Tested WebSocket (native & jsr356 API)
-- Jeanfrancois
Regards
Violeta
---
On 2014-05-20, 6:04 AM, Violeta Georgieva wrote:
The proposed 7.0.54 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.54 Stable
Tested AsyncContext & NIO (usual Atmosphere Framework Testing)
-- Jeanfrancois
Regards
Violeta
---
On 2014-05-16, 4:55 PM, Mark Thomas wrote:
The proposed 8.0.8 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.8 (alpha)
[ ] Beta - go ahead and release as 8.0.8 (beta)
[X] Stable - go ahead and release as 8.0.8 (stable)
Tested WebSocket and AsyncContext, NIO a
Seems
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.6/
is private as I do get a "Not Found"
-- Jeanfrancois
On 2014-05-14, 7:39 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.6 release is now available for voting.
The main changes since 8.0.5 are:
- Further NIO2 fixes wh
The proposed 7.0.53 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.53 Stable
Tested WebSocket & AsyncContext.
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For add
The proposed 8.0.5 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.5 (alpha)
[ ] Beta - go ahead and release as 8.0.5 (beta)
[X] Stable - go ahead and release as 8.0.5 (stable)
Tested WebSockets + AsyncContext
-- Jeanfrancois
--
On 2014-03-19, 5:14 PM, Mark Thomas wrote:
http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_4/
The proposed 8.0.4 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.4 (alpha)
[ ] Beta - go ahead and release as 8.0.4 (beta)
[X] Stable - go ahead and
On 2/13/2014, 3:17 AM, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.52 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.52/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapache
On 2/7/2014, 1:16 PM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.3 release is now available for voting.
The main changes since 8.0.2 are:
- Fix DBCP build
- Update DBCP version to include recent fix for running under a
security manager without needed to grant additional permissions
On 1/29/2014, 6:43 PM, Mark Thomas wrote:
The proposed 8.0.1 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.1 (alpha)
[ ] Beta - go ahead and release as 8.0.1 (beta)
[X] Stable - go ahead and release as 8.0.1 (stable)
Tested jsr356 and Servlet AsyncContext, ta
+1
-- Jeanfrancois
On 1/24/2014, 9:14 AM, Mark Thomas wrote:
Folks,
The ASF discourages (at least it has for as long as I have been around)
the use of @author tags. While I have no wish to remove an existing
@author tag of an author that wants it to stay, I am more than happy to
do the leg work
On 1/17/2014, 3:17 PM, Mark Thomas wrote:
The proposed 6.0.38 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 6.0.38 Stable
Quick sanity check using Atmosphere, tested NIO/CometProcessor and BIO,
no regression found.
-- Jeanfrancois
On 12/20/2013, 7:52 AM, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.50 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.50/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapach
On 2013-12-19 1:38 PM, Mark Thomas wrote:
The proposed 8.0.0-RC10 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 8.0.0-RC10 alpha
Tested jsr356 & AsyncContext with Atmosphere, no issue.
-- Jeanfrancois
Mark
---
On 2013-12-17 7:59 PM, Mark Thomas wrote:
The proposed 8.0.0-RC9 release is:
[X] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.0-RC9 alpha
Atmosphere stopped working with 8.0.0-RC9. With all previous RC from 1
to 7 it worked (didn't test 8) and websockets properly handled for
On 2013-12-11 6:24 PM, Mark Thomas wrote:
The proposed 8.0.0-RC7 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 8.0.0-RC7 alpha
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.ap
On 2013-10-18 7:14 AM, Violeta Georgieva wrote:
The proposed 7.0.47 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.47 Stable
Did we say we will this message as a warning instead of info:
INFO: JSR 356 WebSocket (Java WebSocket 1.0) support is not available
w
[X] Alpha - go ahead and release as 8.0.0-RC4 alpha
Focused on websocket testing, default configuration.
-- Jeanfrancois
On 2013-10-15 8:48 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
for voting.
Given this is a release candidate I am working
[X] Stable - go ahead and release as 7.0.45 Stable
-- Jeanfrancois
On 2013-09-25 9:37 AM, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.45 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionali
On 2013-09-23 4:58 PM, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.44 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
It can be obtained from:
https://dist.apache.org
[X] Alpha - go ahead and release as 8.0.0-RC3 alpha
Tested with Atmosphere jsr356 and Servlet 3 Async API.
-- Jeanfrancois
On 2013-09-20 6:36 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
for voting.
Given this is a release candidate I am working
On 2013-09-20 7:05 AM, Mark Thomas wrote:
On 20/09/2013 11:57, Jeanfrancois Arcand wrote:
On 2013-09-20 6:26 AM, Mark Thomas wrote:
On 20/09/2013 11:24, Jeanfrancois Arcand wrote:
Hi,
[X] Broken - do not release
I do test/use Tomcat with WebSocket since 7.0.27. 8.0.0-RC1 worked well
with
On 2013-09-20 6:26 AM, Mark Thomas wrote:
On 20/09/2013 11:24, Jeanfrancois Arcand wrote:
Hi,
[X] Broken - do not release
I do test/use Tomcat with WebSocket since 7.0.27. 8.0.0-RC1 worked well
with jsr356, but 7.0.43 is broken. You can try it by deploying
http://search.maven.org
One more observation. If I force Atmosphere to use the Tomcat Native
WebSocket API instead of jsr 356, the 7.0.43 works fine as well. So only
jsr356 is broken.
-- Jeanfrancois
On 2013-09-20 6:24 AM, Jeanfrancois Arcand wrote:
Hi,
[X] Broken - do not release
I do test/use Tomcat with
Hi,
[X] Broken - do not release
I do test/use Tomcat with WebSocket since 7.0.27. 8.0.0-RC1 worked well
with jsr356, but 7.0.43 is broken. You can try it by deploying
http://search.maven.org/remotecontent?filepath=org/atmosphere/samples/atmosphere-chat/2.0.0/atmosphere-chat-2.0.0.war
This ap
The proposed 7.0.40 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.40 Stable
Tested with Atmosphere Framework both Comet and WebSocket.
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubsc
[X] Stable - go ahead and release as 7.0.37 Stable
Ran Atmosphere's samples and tests for websocket, native comet and servlet 3
async API without issue.
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.
+1
The Atmosphere Frameworks works well on top of it, bot with HTTP and
WebSockets.
-- Jeanfrancois
On 12-09-02 3:03 AM, Mark Thomas wrote:
The proposed Apache Tomcat 7.0.30 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/
Salut,
try AHC: https://github.com/sonatype/async-http-client
A+
-- Jeanfrancois
On 12-04-12 11:27 AM, Finckler, Christian wrote:
Hello,
after the update I came further. The server now send the upgrade protocol
response.
But jwebsocket doesnt understand the response correctly.
I posted on th
Hi Mark,
sorry for the delay...vacation time :-)
Subject: TC6 source file licensing - last few files
Date: Sun, 05 Aug 2007 00:25:50 -0400
From: Mark Thomas <[EMAIL PROTECTED]>
Reply-To: Tomcat Developers List
To: Tomcat Developers List
All,
Sorry about the deluge of commit mails this eveni
According to the release process, the 6.0.13 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
-- Jeanfrancois
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Remy Maucherat wrote:
Candidate binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.10/
According to the (slightly) updated release process, the 6.0.10 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
Rémy
---
+1
Remy Maucherat wrote:
Hi,
I propose the following release process for Tomcat 6.0.x:
1. create tarball and unofficial binaries, put them on
people.apache.org/~remm/tomcat-6
2. announce candidate binaries are available for testing
3. wait 2-3 days for testing
4. call for alpha/beta/stable v
6.0.7 is:
[ ] Alpha
[X] Beta
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Remy Maucherat wrote:
Kevan Miller wrote:
Well, that's certainly the way it to be, IMO. However, the
xsd's (e.g.
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/javax/servlet/resources/j2ee_1_4.xsd)
are copyrighted by Sun and distribution is explicitly disallowed
without authoriz
6.0.2 is:
[ ] Alpha
[X] Beta
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[X] +1
[ ] +0
[ ] -1
-- Jeanfrancois
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Tomcat v5.5.20 is:
[ X] +1 Stable - no major issues
-- Jeanfrancois
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Greg Wilkins wrote:
Just a notice that I have taken a copy of the 2.5 servlet API for the
geronimo-specs project.
This was done as an SVN copy from
https://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/javax/servlet
to
https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo
Apache Tomcat v5.5.17 is:
[X] Stable - no major issues
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Tomcat v5.5.16 is:
[X ] Stable (no major issues)
[ ] Beta (at least one major issue: please provide details)
[ ] Alpha (multiple significant issues: please provide details)
Minor: when I stress APR with ab,
ab -n1000 -c300 -k http://perf-v4.sfbay.sun.com:8080/images.jar
I'm seeing
Hi Yoav,
Yoav Shapira wrote:
Hi,
A user pointed out to me that our nightly builds appear to be broken.
First I assumed it was due Gump unhappiness and I thought Mark T and
Bill B fixed it over the past few days. But last night's builds still
look whacky: http://cvs.apache.org/builds/jakarta-t
[ X ] Stable - no major issues
[ ] Beta - at least one significant issue (what is it?)
[ ] Alpha - multiple significant issues, not recommended for use (why?)
-- Jeanfrancois
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hi,
I'm currently looking at a corner case when an UnavailableException is
thrown. Mainly, the Servlet is doing:
> public void service(HttpServletRequest req, HttpServletResponse resp)
> throws ServletException, IOException {
>
> PrintWriter out = resp.getWriter();
>
Hi,
I'm currently looking at a corner case when an UnavailableException is
thrown. Mainly, the Servlet is doing:
public void service(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException {
PrintWriter out = resp.getWriter();
resp.s
Costin Manolache wrote:
I wonder what Bob does when his Windows XP is crashing or catches a virus :-)
Well, at least whoever reads the user mail at MSFT is paid for reading
his rants, we're not. And they got his money too.
As for the 'validate' flag - maybe we should just remove it:
- it slows
Hi,
Bob Bronson wrote:
Hello,
Sorry, to bother the developer group with this question but I posted
twice on the user group and received zero replies. I was hoping one of
you could offer some quick advice on this question.
-
I'm using TC 5.5.12.
Please look at
Hi,
Yoav Shapira wrote:
Hi,
I'm curious about the importance of nightly snapshots: who uses them? We have
a nightly source tarball already available at
http://cvs.apache.org/builds/jakarta-tomcat-5/nightly/, so this seems
redundant. If neither you (Henri) nor I knew about it in the years we'v
61 matches
Mail list logo
