[
https://issues.apache.org/jira/browse/TAP5-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376813#comment-15376813
]
Barry Books commented on TAP5-2548:
-----------------------------------
I think this would mostly affect test cases and testing and I would prefer not
to mess with those when upgrading.
I would create new non versioned name, leave the old ones and deprecate them.
I suppose you could make the old ones refuse to run unless the correct version
if found in the classpath.
> Upgrade embedded Jetty and Tomcat versions
> ------------------------------------------
>
> Key: TAP5-2548
> URL: https://issues.apache.org/jira/browse/TAP5-2548
> Project: Tapestry 5
> Issue Type: Dependency upgrade
> Components: tapestry-runner
> Reporter: Jochen Kemnade
> Assignee: Jochen Kemnade
> Labels: desired_for_5.5, patch
> Fix For: 5.5.0
>
> Attachments:
> 0001-TAP5-2548-upgrade-embedded-Tomcat-and-Jetty-versions.patch
>
>
> Since we are switching to Servlet 3.0 for Tapestry 5.5, we should upgrade the
> embedded server versions.
> Unfortunately the runner classes contain the servlet container versions in
> their class names (Jetty7Runner and Tomcat6Runner). This means we can either
> stay backward compatible and confuse users (e.g. start Jetty 8 from
> Jetty7Runner) or rename the classes and break backward compatibility. I
> prefer the latter.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
