Re: Upcoming work
Hi, > I also think 5.5.11 looks good (assuming people did test it; please test > it, I fixed all the bad APR bugs in 5.5.10 that I was aware of, and the > Windows installer also installs an APR/OpenSSL binary is the "native" > option is checked), but the stable build should have the > tomcat.apache.org branding. > > How about doing that this week and then releasing a 5.5.12 build ? Yes, great timing, let's do it. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Yoav Shapira wrote: Yup. 5.5.11 should be a good step in that direction: I'll download and play around with it, but I think the changelog looks great in that it's mostly fixes to known issues, nothing crazy, and therefore should make a good build. I also think 5.5.11 looks good (assuming people did test it; please test it, I fixed all the bad APR bugs in 5.5.10 that I was aware of, and the Windows installer also installs an APR/OpenSSL binary is the "native" option is checked), but the stable build should have the tomcat.apache.org branding. How about doing that this week and then releasing a 5.5.12 build ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Yoav Shapira wrote: Howdy, I am now on the expert group, and it's only a maintenance release (so no new JSR). Ah, good. That's a good point of synergy for us. So it's a new maintenance release, no new JSR, but it will be called Servlet Specification v2.5? And accordingly, Tomcat 6.0... Pretty much. There's JSP 2.1 which is more significant, and given my level of expertise in JSP, it's a problem. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Yoav Shapira wrote: Hola, I'm virtually back from vacation ;) Still traveling, but now for business, and therefore lugging my laptop along. Thank you for the inquiry ;) --- Ashly Mathew Varghese <[EMAIL PROTECTED]> wrote: Just out of context.. What happened to Yoav? - Migrate to tomcat.apache.org. IIRC, we were going to do that after the SVN migration. Mark is doing a great job with the SVN task, with Henri and infra's help. I'd estimate no more than another month to complete the SVN migration, right? The SVN migration for "site" should now be in progress. - Release a new stable 5.5.x. Yup. 5.5.11 should be a good step in that direction: I'll download and play around with it, but I think the changelog looks great in that it's mostly fixes to known issues, nothing crazy, and therefore should make a good build. - Implement Servlet API 2.5: http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/servlet-2_5-changelog.html There are few changes, except support for some annotations (which are optional, but as Tomcat supports all web related optional J2EE features ...). The result would be very similar with Tomcat 5.5, with the possibility of Java 5 related code cleanups (Servlet API 2.5 mandates Java 5). Yes. I have to say I'm happy with the current Servlet 2.5 draft: from our perspective, it's not much serious new work, we can remove a couple of annoying special case paths through the code, and we get to dismiss the compat package. We may want to continue making 5.5 releases for a little while after Tomcat 6.0 is out, as I expect a bunch of users will still using JDK 1.4. Side note on this: the name for the CVS (or actually, SVN) area for Servlet API 2.5. I'd prefer servletapi-2.5 for clarity, even though it breaks the pattern of jakarta-servletapi and then jakarta-servletapi-5 that we have used to date. I agree, it's a very good idea. - Implement JSP 2.1: it's a significant effort, and the issue is that there doesn't seem to be anyone available. Any ideas ? The biggest unaddressed issue on the table at the moment, I agree. I need to look through the spec draft myself. Are the gurus (kin-man, etc.) not around and not available to help out? No idea, but it seems not. MyFaces is going to need the new EL as well. Also, similar side note on CVS/SVN location: perhaps we put it in jspapi-2.1 instead of servletapi-6? Right. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Howdy, > I am now on the expert group, and it's only a maintenance release (so no > new JSR). Ah, good. That's a good point of synergy for us. So it's a new maintenance release, no new JSR, but it will be called Servlet Specification v2.5? And accordingly, Tomcat 6.0... Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Yoav Shapira wrote: Hi, You know, come to think of it, who's on the Spec team for 2.5? I don't even see a formal JSR for it, only the preliminary changelog URL Remy originally posted, which is hanging off the JSR 154 / Servlet Spec 2.4 site. I am now on the expert group, and it's only a maintenance release (so no new JSR). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Hi, You know, come to think of it, who's on the Spec team for 2.5? I don't even see a formal JSR for it, only the preliminary changelog URL Remy originally posted, which is hanging off the JSR 154 / Servlet Spec 2.4 site. Yoav --- Remy Maucherat <[EMAIL PROTECTED]> wrote: > Mark Thomas wrote: > > Remy Maucherat wrote: > > > >> Mark Thomas wrote: > >> > >>> I think the spec team get to decide this. I had assumed they would do > >>> something similar to the servletapi-5 and have jsr154 and jsr245 > >>> directories under the root directory (which in svn would be > >>> \tomcat\servletapi\trunk - the current trunk having been moved to > >>> \tomcat\servletapi\branches\tc5.x.x\). > >> > >> > >> I don't know if the spec team is actually still responsible for these > >> repositories, such as if they intend to add the Servlet 2.5 / JSP 2.1 > >> API source there. If the don't, we can switch to a more OSS friendly > >> access and management style. > > > > Who do we need to talk at the spec team about this? > > At least Jan would know, and he seems to be reading the list. Maybe they > haven't quite decided what to do. > > Rémy > > - > 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: Upcoming work
Mark Thomas wrote: Remy Maucherat wrote: Mark Thomas wrote: I think the spec team get to decide this. I had assumed they would do something similar to the servletapi-5 and have jsr154 and jsr245 directories under the root directory (which in svn would be \tomcat\servletapi\trunk - the current trunk having been moved to \tomcat\servletapi\branches\tc5.x.x\). I don't know if the spec team is actually still responsible for these repositories, such as if they intend to add the Servlet 2.5 / JSP 2.1 API source there. If the don't, we can switch to a more OSS friendly access and management style. Who do we need to talk at the spec team about this? At least Jan would know, and he seems to be reading the list. Maybe they haven't quite decided what to do. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Remy Maucherat wrote: Mark Thomas wrote: I think the spec team get to decide this. I had assumed they would do something similar to the servletapi-5 and have jsr154 and jsr245 directories under the root directory (which in svn would be \tomcat\servletapi\trunk - the current trunk having been moved to \tomcat\servletapi\branches\tc5.x.x\). I don't know if the spec team is actually still responsible for these repositories, such as if they intend to add the Servlet 2.5 / JSP 2.1 API source there. If the don't, we can switch to a more OSS friendly access and management style. Who do we need to talk at the spec team about this? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Mark Thomas wrote: I think the spec team get to decide this. I had assumed they would do something similar to the servletapi-5 and have jsr154 and jsr245 directories under the root directory (which in svn would be \tomcat\servletapi\trunk - the current trunk having been moved to \tomcat\servletapi\branches\tc5.x.x\). I don't know if the spec team is actually still responsible for these repositories, such as if they intend to add the Servlet 2.5 / JSP 2.1 API source there. If the don't, we can switch to a more OSS friendly access and management style. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Yoav Shapira wrote: I'd estimate no more than another month to complete the SVN migration, right? Work commitments permitting, certainly within a month and quite possibly less. Side note on this: the name for the CVS (or actually, SVN) area for Servlet API 2.5. I'd prefer servletapi-2.5 for clarity, even though it breaks the pattern of jakarta-servletapi and then jakarta-servletapi-5 that we have used to date. My original svn migration proposal suggested \servletapi\ \trunk\ \branches\ \tc3.x.x\ \tc4.x.x\ \other\ \tags\ \tc3.x.x\ \tc4.x.x\ \other\ I like keeping the directory naming aligned with the rest of the Tomcat repository. It makes it easier for new users to find their way around. As part of the new TLP site, we need to add areas that have previously been handled by Jakarta including version control repositories. I think this is where we make the mapping between Tomcat versions and Servlet/JSP versions clear. Also, similar side note on CVS/SVN location: perhaps we put it in jspapi-2.1 instead of servletapi-6? I think the spec team get to decide this. I had assumed they would do something similar to the servletapi-5 and have jsr154 and jsr245 directories under the root directory (which in svn would be \tomcat\servletapi\trunk - the current trunk having been moved to \tomcat\servletapi\branches\tc5.x.x\). Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Upcoming work
Hola, I'm virtually back from vacation ;) Still traveling, but now for business, and therefore lugging my laptop along. Thank you for the inquiry ;) --- Ashly Mathew Varghese <[EMAIL PROTECTED]> wrote: > Just out of context.. What happened to Yoav? > - Migrate to tomcat.apache.org. IIRC, we were going to do that after the SVN migration. Mark is doing a great job with the SVN task, with Henri and infra's help. I'd estimate no more than another month to complete the SVN migration, right? > - Release a new stable 5.5.x. Yup. 5.5.11 should be a good step in that direction: I'll download and play around with it, but I think the changelog looks great in that it's mostly fixes to known issues, nothing crazy, and therefore should make a good build. > - Implement Servlet API 2.5: > http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/servlet-2_5-changelog.html > There are few changes, except support for some annotations (which are > optional, but as Tomcat supports all web related optional J2EE features > ...). The result would be very similar with Tomcat 5.5, with the > possibility of Java 5 related code cleanups (Servlet API 2.5 mandates > Java 5). Yes. I have to say I'm happy with the current Servlet 2.5 draft: from our perspective, it's not much serious new work, we can remove a couple of annoying special case paths through the code, and we get to dismiss the compat package. We may want to continue making 5.5 releases for a little while after Tomcat 6.0 is out, as I expect a bunch of users will still using JDK 1.4. Side note on this: the name for the CVS (or actually, SVN) area for Servlet API 2.5. I'd prefer servletapi-2.5 for clarity, even though it breaks the pattern of jakarta-servletapi and then jakarta-servletapi-5 that we have used to date. > - Implement JSP 2.1: it's a significant effort, and the issue is that > there doesn't seem to be anyone available. Any ideas ? The biggest unaddressed issue on the table at the moment, I agree. I need to look through the spec draft myself. Are the gurus (kin-man, etc.) not around and not available to help out? Also, similar side note on CVS/SVN location: perhaps we put it in jspapi-2.1 instead of servletapi-6? Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Upcoming work
Ashly Mathew Varghese wrote: Just out of context.. What happened to Yoav? He's on vacation. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Upcoming work
Just out of context.. What happened to Yoav? +ashly -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Sunday, August 28, 2005 6:49 PM To: tomcat-dev@jakarta.apache.org Subject: Upcoming work There are quite a few tasks ahead: - Migrate to tomcat.apache.org. - Release a new stable 5.5.x. - New SVN repositories. - Implement Servlet API 2.5: http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/servlet-2_5-changelog.html There are few changes, except support for some annotations (which are optional, but as Tomcat supports all web related optional J2EE features ...). The result would be very similar with Tomcat 5.5, with the possibility of Java 5 related code cleanups (Servlet API 2.5 mandates Java 5). - Implement JSP 2.1: it's a significant effort, and the issue is that there doesn't seem to be anyone available. Any ideas ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
