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

ASF subversion and git services commented on WW-5030:
-----------------------------------------------------

Commit 5003e093b9e5652a24acd3adcc84e51086908a15 in struts's branch refs/heads/action-context-boost from Lukasz Lenart
[ https://gitbox.apache.org/repos/asf?p=struts.git;h=5003e09 ]

Merge pull request #398 from JCgH4164838Gh792C124B5/WW-5030_Proposed_Change

Proposed implementation to address WW-5030.

> ClassNotFoundException - MockPortletResponse
> --------------------------------------------
>
>                 Key: WW-5030
>                 URL: https://issues.apache.org/jira/browse/WW-5030
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Portlet
>    Affects Versions: 2.5.18
>            Reporter: John Bush
>            Priority: Major
>             Fix For: 2.6
>
>         Attachments: TestStrutsPortlet.zip, fail.txt, success.txt
>
>
> WW-3826 solved a problem running JUnit tests on portlet actions that use the struts2-portlet-plugin and struts2-junit-plugin. The solution used Spring's org.springframework.mock.web.portlet package in the spring-test framework. Spring Portlet MVC is no longer supported (SPR-14129) and the package has been removed starting with Spring 5. I'm not able to upgrade to Spring 5 without loosing my unit testing since having both versions of spring-test in my classpath creates many other issues.
> I've attached a zipped portlet project for testing (TestStrutsPortlet.zip), console log from a successful test (success.txt) and console log from a failed test (fail.txt). All that needs to change is the spring-version in the POM to recreate the testing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)