Re: [5.0] Schedule change
Remy Maucherat wrote: Reshat Sabiq wrote: I'm a newbie on this list, but i think 2.4/2.0 draft 3 5.0.14 is a good idea. At least it's more specific than Beta. P.S. Btw, as far as bugs i couldn't use custom error pages in Sun's 1.4 Beta 2 (Tomcat 5). Reported to Sun, and they forwarded me to Apache, and i didn't have time. Could report that on BZ. It might of course all be my fault, but it works in 4.1, and 4.2. There are tests for that in both the tester and watchdog, so you'll have to submit a test WAR. (BTW, there's no 4.2) My bad. I meant 4.1.1, and 4.1.2 (i've used 4.1.8, 4.1.9, 4.1.12, and 4.1.24). How do i submit a test war to tester or watchdog (i only know Bugzilla). Thanks. -- Sincerely, Reshat. --- If you see my certificate with this message, you should be able to send me encrypted e-mail. Please consult your e-mail client for details if you would like to do that. smime.p7s Description: S/MIME Cryptographic Signature
Re: [5.0] Schedule change
Reshat Sabiq wrote: My bad. I meant 4.1.1, and 4.1.2 (i've used 4.1.8, 4.1.9, 4.1.12, and 4.1.24). How do i submit a test war to tester or watchdog (i only know Bugzilla). No, if you have a test case, submit it in BZ. The tester and watchdog are the test suites we use. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Hans/Remy, I don't know more than you do about when J2EE 1.4 will be released, but the specs are starting to move through final approval now, so I'm pretty sure it will happen in a month or two. Three months for running a few Beta releases instead of releasing it as something it's not doesn't seem to bad to me ... Sun expects to ship J2EE 1.4 FCS sometime around the last week of November. Hope this helps. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
By the way, is there any plan to certify Tomcat 5? As everyone knows, Sun controls the RI now. While it's rumored to be based on Tomcat code, that's not the same thing. Also, as everyone knows, Geronimo is planning to test the Sun/Apache agreement by getting the test-suite under the Sun/Apache agreement to certify them as a JSEE container once they've gotten up and running. I really think that Tomcat should request the test-suite for Servlet 2.4/JSP 2.0. At the very least, it might give Remy something to do while waiting for the specs to go final ;-). Remy Maucherat [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Bill Barker wrote: By the way, is there any plan to certify Tomcat 5? As everyone knows, Sun controls the RI now. While it's rumored to be based on Tomcat code, that's not the same thing. Also, as everyone knows, Geronimo is planning to test the Sun/Apache agreement by getting the test-suite under the Sun/Apache agreement to certify them as a JSEE container once they've gotten up and running. I really think that Tomcat should request the test-suite for Servlet 2.4/JSP 2.0. At the very least, it might give Remy something to do while waiting for the specs to go final ;-). It sounds like a good idea. Thanks for volunteering ! :-D Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Wednesday, October 01, 2003 12:05 AM Subject: Re: [5.0] Schedule change Bill Barker wrote: By the way, is there any plan to certify Tomcat 5? As everyone knows, Sun controls the RI now. While it's rumored to be based on Tomcat code, that's not the same thing. Also, as everyone knows, Geronimo is planning to test the Sun/Apache agreement by getting the test-suite under the Sun/Apache agreement to certify them as a JSEE container once they've gotten up and running. I really think that Tomcat should request the test-suite for Servlet 2.4/JSP 2.0. At the very least, it might give Remy something to do while waiting for the specs to go final ;-). It sounds like a good idea. Thanks for volunteering ! :-D Great. You give just about the only person on the project that's not in the PMC the job ;-). I'll do my best. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Bill Barker wrote: Bill Barker wrote: Great. You give just about the only person on the project that's not in the PMC the job ;-). I'll do my best. Come on, don't let small details stop you (and it's easy to do a vote on the PMC list anyway) ;-) BTW, small glitch: can you actually get the test suite before the spec is released ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Reshat Sabiq wrote: I'm a newbie on this list, but i think 2.4/2.0 draft 3 5.0.14 is a good idea. At least it's more specific than Beta. P.S. Btw, as far as bugs i couldn't use custom error pages in Sun's 1.4 Beta 2 (Tomcat 5). Reported to Sun, and they forwarded me to Apache, and i didn't have time. Could report that on BZ. It might of course all be my fault, but it works in 4.1, and 4.2. There are tests for that in both the tester and watchdog, so you'll have to submit a test WAR. (BTW, there's no 4.2) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Bill Barker wrote: By the way, is there any plan to certify Tomcat 5? As everyone knows, Sun controls the RI now. While it's rumored to be based on Tomcat code, that's not the same thing. Also, as everyone knows, Geronimo is planning to test the Sun/Apache agreement by getting the test-suite under the Sun/Apache agreement to certify them as a JSEE container once they've gotten up and running. I really think that Tomcat should request the test-suite for Servlet 2.4/JSP 2.0. At the very least, it might give Remy something to do while waiting for the specs to go final ;-). BTW, we are running the TCKs (JSP/Servlet/JSTL) on Tomcat nightly build every day. Currently all tcks are passing... We can certainly help getting/setting the tcks if required. The Axis team is currently running the tcks by their own right now. -- Jeanfrancois Remy Maucherat [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Why don't you keep TC5.0 in beta and branch and start work on TC5.1? Dave. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Dave Oxley wrote: Why don't you keep TC5.0 in beta and branch and start work on TC5.1? The thing is, I don't have brilliant new features ideas, sorry to disappoint :-( I do have *some* which are relatively useful, but nearly all are modules, and can be done independently of the core (ie, there's no need for branching). Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.0] Schedule change
Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0] Schedule change
Howdy, I think many people are waiting for tomcat 5 as a servlet 2.4 implementation. Not more, not less. While it has many other great features, that's the main one, and there's no point in releasing it until then IMHO ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 2:28 PM To: Tomcat Developers List Subject: [5.0] Schedule change Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
+1 It may be better to get an official release out sooner than later. In a worst case where the spec is changed from what is expected, tomcat 5.2 could address that. -Tim Remy Maucherat wrote: Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Remy Maucherat wrote: Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? What about releasing it as tomcat4.2 ( since many people assume 4.x is the implementation series for servlet 2.3 ) ? Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 11:27 AM Subject: [5.0] Schedule change Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? You can be a Servlet 2.3 container, or you can be a Servlet 2.4 container, but not both (see for example, BZ #23525). I agree with Yoav that what people want most from Tomcat 5 is a Servlet 2.4/JSP 2.0 container. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Bill Barker wrote: You can be a Servlet 2.3 container, or you can be a Servlet 2.4 container, but not both (see for example, BZ #23525). I agree with Yoav that what Well, Sun is claiming full compatibility, so I'm assuming it's fully compatible :) people want most from Tomcat 5 is a Servlet 2.4/JSP 2.0 container. There are only bad solutions here: - wait for an unspecified, and possibly long, amount of time, sitting on a finished product - backport patches (we probably don't have the resources, and destabilizing 4.1 would be bad; we'd have to use a new 4.2 branch) - branch a new 4.2 based on the current 5.0, and remove features (IMO it doesn't make any sense, plus that would destabilize the codebase - a bit less than the previous option, however -, and run into a similar resources issues) If the first option is chosen, I will go work on other stuff (at JBoss) while the project stays idle (chômage technique, as we say in French). As you all know: no stable release = no testers = no bugs = nothing to fix :-( I don't have any time to dedicate to either of the other two options, as I have neither motivation nor need for such a product. Sorry :-( So I think we're stuck :-( Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Remy Maucherat wrote: Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? How much work is it to revert Tomcat 5 back to Sevlet 2.3/JSP 1.2? And I agree with Costin that we should keep the major revision tied to the versions of the Servlet/JSP spec. Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Glenn Nielsen wrote: How much work is it to revert Tomcat 5 back to Sevlet 2.3/JSP 1.2? If you want to really remove the features, I think it's significant. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Remy Maucherat wrote: Bill Barker wrote: [...] people want most from Tomcat 5 is a Servlet 2.4/JSP 2.0 container. There are only bad solutions here: - wait for an unspecified, and possibly long, amount of time, sitting on a finished product - backport patches (we probably don't have the resources, and destabilizing 4.1 would be bad; we'd have to use a new 4.2 branch) - branch a new 4.2 based on the current 5.0, and remove features (IMO it doesn't make any sense, plus that would destabilize the codebase - a bit less than the previous option, however -, and run into a similar resources issues) If the first option is chosen, I will go work on other stuff (at JBoss) while the project stays idle (chômage technique, as we say in French). As you all know: no stable release = no testers = no bugs = nothing to fix :-( I'm pretty sure that if you release a TC 5 Beta, you will get quite a few people to test it, and unless it's already perfect, they will find bugs. I don't know more than you do about when J2EE 1.4 will be released, but the specs are starting to move through final approval now, so I'm pretty sure it will happen in a month or two. Three months for running a few Beta releases instead of releasing it as something it's not doesn't seem to bad to me ... I don't have any time to dedicate to either of the other two options, as I have neither motivation nor need for such a product. Sorry :-( Sure, I understand how you feel and no one can force you to work on it, of course, but I hope you do even if it's just Beta for another few months. So I think we're stuck :-( I hope not. Hans -- Hans Bergsten[EMAIL PROTECTED] Gefion Software http://www.gefionsoftware.com/ Author of O'Reilly's JavaServer Pages, covering JSP 1.2 and JSTL 1.0 Details athttp://TheJSPBook.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
Hans Bergsten wrote: Remy Maucherat wrote: If the first option is chosen, I will go work on other stuff (at JBoss) while the project stays idle (chômage technique, as we say in French). As you all know: no stable release = no testers = no bugs = nothing to fix :-( I'm pretty sure that if you release a TC 5 Beta, you will get quite a few people to test it, and unless it's already perfect, they will find bugs. Hehe, we've been in beta for some time. The amount of bugs reported hasn't been staggering (similar to when we were in alpha, I think). Anyway, I think it was the same for TC 4.0: the testing while in beta was an order of magnitude lower. Esp since there's a release which is perceived as good enough out there (4.1). I don't know more than you do about when J2EE 1.4 will be released, but the specs are starting to move through final approval now, so I'm pretty sure it will happen in a month or two. Three months for running a few Beta releases instead of releasing it as something it's not doesn't seem to bad to me ... More than a month in beta already. I think the beta time depends on the situation. We have less new code than in TC 4.0 or 4.1, that's for sure. I think it can be compared to TC 3.2 - TC 3.3 maybe. I don't have any time to dedicate to either of the other two options, as I have neither motivation nor need for such a product. Sorry :-( Sure, I understand how you feel and no one can force you to work on it, of course, but I hope you do even if it's just Beta for another few months. Well, here's what I do in the waiting scenario: - tags once in a while (probably once per month on average) - commit reviews - occasional bugfix as issues come in Anyway, I'll be carefully considering all my options. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0] Schedule change
I might be off base, but whats the problem with releasing TC 5 under the banner of supporting a draft spec. Servlet/JSP SpecTomcat version 2.4/2.0 draft 3 5.0.14 2.3/1.2 4.1.27 2.2/1.1 3.3.1a Chad Johnson Web Services Developer WS Packaging Group, Inc. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 1:28 PM To: Tomcat Developers List Subject: [5.0] Schedule change Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Schedule change
I'm a newbie on this list, but i think 2.4/2.0 draft 3 5.0.14 is a good idea. At least it's more specific than Beta. P.S. Btw, as far as bugs i couldn't use custom error pages in Sun's 1.4 Beta 2 (Tomcat 5). Reported to Sun, and they forwarded me to Apache, and i didn't have time. Could report that on BZ. It might of course all be my fault, but it works in 4.1, and 4.2. Chad Johnson wrote: I might be off base, but whats the problem with releasing TC 5 under the banner of supporting a draft spec. Servlet/JSP Spec Tomcat version 2.4/2.0 draft 3 5.0.14 2.3/1.2 4.1.27 2.2/1.1 3.3.1a Chad Johnson Web Services Developer WS Packaging Group, Inc. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 1:28 PM To: Tomcat Developers List Subject: [5.0] Schedule change Hi, The signals I'm getting from Sun about the schedule of the specifications is highly confusing. Since I'm tired of having Tomcat depend on these, I propose taking advantage of the backwards compatibility of the spec, and replacing the TC 5 statement phrase with: The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications, and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are officially available. That would allow making a timely 5.0 release, rather than expecting stuff for an indefinite amount of time ... If I don't get yelled at too much, I'll call for a vote on this. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sincerely, Reshat. --- If you see my certificate with this message, you should be able to send me encrypted e-mail. Please consult your e-mail client for details if you would like to do that. smime.p7s Description: S/MIME Cryptographic Signature
