Re: Important information about jakarta-servletapi-*
Mark Roth wrote: Unfortunately, the answer is no, even though it seems rather silly. The reason is that the specifications themselves have an auto-generated copy of the javadocs in PDF format, and the assertion list for the TCK is generated, in part, based on the javadoc tags. Converting an incorrect @returns to a correct @return would make both the spec PDF and assertion list get out of sync with the API workspace. There are other side-effects as well. Thanks in advance for the summary to the specification aliases! I think we should refuse reports against the APIs, and direct folks to Sun or the JCP. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Important information about jakarta-servletapi-*
Hi everyone, I've seen a few requests to fix items in the jakarta-servletapi-* workspaces and wanted to clear up any confusion there might be. Changes to examples in these workspaces are fine. However, ANY changes to the core APIs (including even simple javadocs changes) CANNOT be done outside of the JCP process. This applies to both Servlet and JSP APIs. To make any changes to these APIs, you must propose the change through the spec aliases, which appear on the front covers of the corresponding specifications: Servlet: [EMAIL PROTECTED] JSP: [EMAIL PROTECTED] Your change request will be considered by the specification leads and potentially debated by the expert group. Changes to the APIs can only be done in a maintenance release of the specification, or in the next revision of the specification. The Servlet 2.4 and JSP 2.0 specifications have both been finalized for this release of Tomcat and are very unlikely to change in any substantial way until the next release. Please understand that Tomcat is only one of many containers that are implementing the Servlet and JSP specifications, and the APIs must match identically on all containers. Please don't hesitate to contact me if you have any questions on this matter. Thank you for your cooperation. --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Important information about jakarta-servletapi-*
Does this mean that any bug submitted with a criticism (or patch) against jakarta-servletapi-* can be marked as WONTFIX with a advisory for the requestor to notify [EMAIL PROTECTED] or [EMAIL PROTECTED] ? (I know there is at least one bug in this category) -Tim Mark Roth wrote: Hi everyone, I've seen a few requests to fix items in the jakarta-servletapi-* workspaces and wanted to clear up any confusion there might be. Changes to examples in these workspaces are fine. However, ANY changes to the core APIs (including even simple javadocs changes) CANNOT be done outside of the JCP process. This applies to both Servlet and JSP APIs. To make any changes to these APIs, you must propose the change through the spec aliases, which appear on the front covers of the corresponding specifications: Servlet: [EMAIL PROTECTED] JSP: [EMAIL PROTECTED] Your change request will be considered by the specification leads and potentially debated by the expert group. Changes to the APIs can only be done in a maintenance release of the specification, or in the next revision of the specification. The Servlet 2.4 and JSP 2.0 specifications have both been finalized for this release of Tomcat and are very unlikely to change in any substantial way until the next release. Please understand that Tomcat is only one of many containers that are implementing the Servlet and JSP specifications, and the APIs must match identically on all containers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Important information about jakarta-servletapi-*
Howdy, Thanks for the clarification Mark, and for beating me to the question Tim ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 1:09 PM To: Tomcat Developers List Subject: Re: Important information about jakarta-servletapi-* Does this mean that any bug submitted with a criticism (or patch) against jakarta-servletapi-* can be marked as WONTFIX with a advisory for the requestor to notify [EMAIL PROTECTED] or [EMAIL PROTECTED] ? (I know there is at least one bug in this category) -Tim Mark Roth wrote: Hi everyone, I've seen a few requests to fix items in the jakarta-servletapi-* workspaces and wanted to clear up any confusion there might be. Changes to examples in these workspaces are fine. However, ANY changes to the core APIs (including even simple javadocs changes) CANNOT be done outside of the JCP process. This applies to both Servlet and JSP APIs. To make any changes to these APIs, you must propose the change through the spec aliases, which appear on the front covers of the corresponding specifications: Servlet: [EMAIL PROTECTED] JSP: [EMAIL PROTECTED] Your change request will be considered by the specification leads and potentially debated by the expert group. Changes to the APIs can only be done in a maintenance release of the specification, or in the next revision of the specification. The Servlet 2.4 and JSP 2.0 specifications have both been finalized for this release of Tomcat and are very unlikely to change in any substantial way until the next release. Please understand that Tomcat is only one of many containers that are implementing the Servlet and JSP specifications, and the APIs must match identically on all containers. - 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: Important information about jakarta-servletapi-*
Hi Tim, Tim Funk wrote: Does this mean that any bug submitted with a criticism (or patch) against jakarta-servletapi-* can be marked as WONTFIX with a advisory for the requestor to notify [EMAIL PROTECTED] or [EMAIL PROTECTED] ? (I know there is at least one bug in this category) If the bug fix results in a change to the externally-visible portions of an API class (javax.*), the change MUST go through the JCP. The best way to get such an issue considered is through the mail aliases I mentioned in the previous email. Fixing bugs in the implementation of such classes resulting in NO change to the external interface (e.g. signature of public/protected methods or javadocs) is okay. Additions, removals and changes to other portions of this workspace, such as the sample applications, are entirely okay. I'll leave it up to the Tomcat team to decide how to handle the paperwork (e.g. whether to mark bugs as WONTFIX or not). Your suggestion sounds reasonable to me. It's probably a good idea to outline these rules in a README.txt file in the workspace as well. Hope this helps. --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Important information about jakarta-servletapi-*
Hi Yoav, Shapira, Yoav wrote: Howdy, Thanks for the clarification Mark, and for beating me to the question Tim ;) No problem! --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Important information about jakarta-servletapi-*
Mark, One final question. The javadoc bugs I was looking at were of the following types: - @returns used rather than @return - @seealso used rather than @see - etc Is it permitted to make changes to fix these? There were no changes to the actual text of the javadoc. Thanks, Mark On Wednesday, December 17, 2003 6:22 PM, Mark Roth [SMTP:[EMAIL PROTECTED] wrote: Hi Yoav, Shapira, Yoav wrote: Howdy, Thanks for the clarification Mark, and for beating me to the question Tim ;) No problem! --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. - 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: Important information about jakarta-servletapi-*
Hi Mark, Mark Thomas wrote: Mark, One final question. The javadoc bugs I was looking at were of the following types: - @returns used rather than @return - @seealso used rather than @see - etc Yuck. :) It's unfortunate we didn't catch those earlier. I'm definitely interested in a list of any such bugs in the JSP APIs and I'm sure Yutaka is too, for Servlet. Please send a summary of any such errors to the spec aliases and we'll be sure to catch them in the next revision of the specs. Is it permitted to make changes to fix these? There were no changes to the actual text of the javadoc. Unfortunately, the answer is no, even though it seems rather silly. The reason is that the specifications themselves have an auto-generated copy of the javadocs in PDF format, and the assertion list for the TCK is generated, in part, based on the javadoc tags. Converting an incorrect @returns to a correct @return would make both the spec PDF and assertion list get out of sync with the API workspace. There are other side-effects as well. Thanks in advance for the summary to the specification aliases! --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
