You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/10/08 21:39:00 UTC
[jira] [Commented] (TAP5-2644) Split HTTP-specific classes from
tapestry-core into tapestry-http
[ https://issues.apache.org/jira/browse/TAP5-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210473#comment-17210473 ]
ASF subversion and git services commented on TAP5-2644:
-------------------------------------------------------
Commit c9668b894efaf3b1c8bd267f47d21882ed1a2ece in tapestry-5's branch refs/heads/java9modules from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=c9668b8 ]
TAP5-2644: split tapestry-http out of tapestry-core
> Split HTTP-specific classes from tapestry-core into tapestry-http
> -----------------------------------------------------------------
>
> Key: TAP5-2644
> URL: https://issues.apache.org/jira/browse/TAP5-2644
> Project: Tapestry 5
> Issue Type: Improvement
> Reporter: Thiago Henrique De Paula Figueiredo
> Priority: Major
>
> The intention is moving the HTTP-specific classes of tapestry-core (HttpServletResquestFilter, RequestFilter, Dispatcher, Response, Request, etc.) moved into a new subproject/JAR, tapestry-http, where it could be used without the component/page framework. Backward compatibility, other than classes changing from one package to another, should be kept.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)