Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support
What don't you understand about my comment? It seems short but fairly clear to me. david jencks On Sep 9, 2004, at 12:01 PM, Dain Sundstrom wrote: David, Can you update this issue to reflect what is actually broken or open a new issue? -dain On Sep 9, 2004, at 9:49 AM, [EMAIL PROTECTED] wrote: Message: The following issue has been reopened. Reopener: David Jencks Date: Thu, 9 Sep 2004 9:48 AM taglib tags move into jsp-config tag. This is not handled by jetty. - View the issue: http://issues.apache.org/jira/browse/GERONIMO-278 Here is an overview of the issue: - Key: GERONIMO-278 Summary: Servlet/JSP 2.3 DTD deployment descriptor support Type: New Feature Status: Reopened Priority: Major Project: Apache Geronimo Components: web Fix Fors: 1.0-M2 Versions: 1.0-M1 Assignee: David Jencks Reporter: David Blevins Created: Thu, 29 Jul 2004 5:53 PM Updated: Thu, 9 Sep 2004 9:48 AM Description: Servlet/JSP 2.2 DTD deployment descriptor support - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support
in web-app 2.3, taglib was at the same level as servlet, servlet-mapping etc. In 2.4 it is moved into a jsp-config tag. The 2.3 to 2.4 conversion in M2 did not move the taglib tags. I changed the schema conversion util to move the taglib tags into a new jsp-config tag. I can add this verbose comment if you want, but I don't really understand the pattern of reopening and reclosing I've been seeing, so I won't until I get some advice on the procedure you have been following. Or, you can add it. david jencks On Sep 9, 2004, at 12:19 PM, Dain Sundstrom wrote: What wasn't working in M2 that you just fixed? -dain On Sep 9, 2004, at 10:15 AM, David Jencks wrote: What don't you understand about my comment? It seems short but fairly clear to me. david jencks On Sep 9, 2004, at 12:01 PM, Dain Sundstrom wrote: David, Can you update this issue to reflect what is actually broken or open a new issue? -dain On Sep 9, 2004, at 9:49 AM, [EMAIL PROTECTED] wrote: Message: The following issue has been reopened. Reopener: David Jencks Date: Thu, 9 Sep 2004 9:48 AM taglib tags move into jsp-config tag. This is not handled by jetty. - View the issue: http://issues.apache.org/jira/browse/GERONIMO-278 Here is an overview of the issue: - Key: GERONIMO-278 Summary: Servlet/JSP 2.3 DTD deployment descriptor support Type: New Feature Status: Reopened Priority: Major Project: Apache Geronimo Components: web Fix Fors: 1.0-M2 Versions: 1.0-M1 Assignee: David Jencks Reporter: David Blevins Created: Thu, 29 Jul 2004 5:53 PM Updated: Thu, 9 Sep 2004 9:48 AM Description: Servlet/JSP 2.2 DTD deployment descriptor support - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support
On Sep 9, 2004, at 10:55 AM, David Jencks wrote: in web-app 2.3, taglib was at the same level as servlet, servlet-mapping etc. In 2.4 it is moved into a jsp-config tag. The 2.3 to 2.4 conversion in M2 did not move the taglib tags. I changed the schema conversion util to move the taglib tags into a new jsp-config tag. I can add this verbose comment if you want, but I don't really understand the pattern of reopening and reclosing I've been seeing, so I won't until I get some advice on the procedure you have been following. Or, you can add it. I'll add it. The reason you have to reopen and reclose, is JIRA doesn't let you change a closed issue. When we were generating the Release Notes last night, we found several issues that were miscategorized, had the wrong version number, or bad descriptions. Hopefully, we can all work to keep JIRA up to date so releases don't take so long to push out. -dain
