tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2548) Upgrade embedded Jetty and Tomcat versions
Date Thu, 21 Jul 2016 12:20:20 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387583#comment-15387583
] 

ASF subversion and git services commented on TAP5-2548:
-------------------------------------------------------

Commit bb0f058de48c1f5229d050c960c70e0523c8cfd9 in tapestry-5's branch refs/heads/master from
[~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=bb0f058 ]

TAP5-2548: create deprecated versions of the old classes that log a warning when they are
instantiated


> 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)

Mime
View raw message