struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (Jira)" <j...@apache.org>
Subject [jira] [Commented] (WW-5030) ClassNotFoundException - MockPortletResponse
Date Sun, 23 Feb 2020 18:42:00 GMT

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

Lukasz Lenart commented on WW-5030:
-----------------------------------

As far I understand we can easily "re-use" any AL2.0 based code, I can ask ASF legal to clarify
this, but I think this is a good direction.

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

Mime
View raw message