[
https://issues.apache.org/jira/browse/TAP5-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220411#comment-17220411
]
Hudson commented on TAP5-2644:
------------------------------
FAILURE: Integrated in Jenkins build Tapestry ยป
tapestry-java9-modules-freestyle #35 (See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-java9-modules-freestyle/35/])
TAP5-2644: fixing tapestry-spring test failures (thiago: rev
da50b7e21d252caac6c9344fa3fb8e5d9d4ca1d4)
* (edit)
tapestry-spring/src/test/java/org/apache/tapestry5/spring/integration/external/TapestryExternalSpringContextIntegrationTest.java
* (edit)
tapestry-spring/src/main/java/org/apache/tapestry5/spring/modules/SpringModule.java
> 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)
