czw., 18 kwi 2019 o 08:10 John Bush napisał(a):
>
> I think that makes sense. Anyone using the portlet-plugin in an
> enterprise setting will want to maintain their testing. I also wondered
> if Spring or the license would allow repackaging the code, especially
> since they no longer support it. S
I think that makes sense. Anyone using the portlet-plugin in an
enterprise setting will want to maintain their testing. I also wondered
if Spring or the license would allow repackaging the code, especially
since they no longer support it. Sorry I didn't open an issue - missed
the request. What
So it would be good to provide our own stubbing classes for
Request/Response? I think we can copy/paste Spring once as they based
on AFL.
niedz., 25 lis 2018 o 17:47 Yasser Zamani napisał(a):
>
> I found Spring officially says:
>
> "The Spring Framework no longer supports: Portlet, Velocity,
> Ja
I found Spring officially says:
"The Spring Framework no longer supports: Portlet, Velocity,
JasperReports, XMLBeans, JDO, Guava (replaced by the Caffeine support).
If those are critical to your project, you should stay on Spring
Framework 4.3.x (supported until 2020). Alternatively, you may creat
The missing package org.springframework.mock.web.portlet was in spring-test. If
you use the appropriate spring-test 5 then struts2-junit-plugin will fail with
class not found. If you test using spring-test 4 then struts2-junit-plugin will
run but all the tests for anything using Spring 5 would
Hi John,
I think it's possible to keep spring updated to 5 and in same time, to
have needed old dependencies in scope `test` to save unit tests, e.g:
org.springframework
spring-test
test
org.springframework
I'm by no means a struts inner-workings expert so the following
statements may totally be wrong. I'm not sure a portlet guru is needed
since the problem isn't in struts2-portlet-plugin. It still provides the
portlet request/response life-cycle emulation for the application
appropriately with no
śr., 14 lis 2018 o 08:48 John Bush napisał(a):
> WW-3826 solved a problem running JUnit tests on portlet actions via
> 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
WW-3826 solved a problem running JUnit tests on portlet actions via
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 be
