What does the future hold for Spring Portlet MVC? Long live PortletMVC4Spring!
It's my pleasure to announce the release of a new project sponsored by Liferay: PortletMVC4Spring.
The PortletMVC4Spring project began as Spring Portlet MVC and was part of the Spring Framework. When the project was pruned from version 5.0.x of the Spring Framework under SPR-14129, it became necessary to fork and rename the project. This made it possible to improve and maintain the project for compatibility with the latest versions of the Spring Framework and the Portlet API.
Liferay adopted Spring Portlet MVC in March of 2019 and the project was renamed to PortletMVC4Spring. Naming credit goes to Milen Dyankov, Head of Developer Relations at Liferay.
PortletMVC4Spring requires JDK 8+ and has been upgraded to version 3.0 of the Portlet API. In addition, it has been refactored and tested for use with version 5.1.x of the Spring Framework.
The project supports the following Portlet 3.0 compliant portals:
On behalf of Liferay, I would like to extend our thanks to Pivotal Software, Inc. and all of the developers that contributed to Spring Portlet MVC including Juergen Hoeller, Chris Beams, Rossen Stoyanchev, Phillip Webb, Markus Malkusch, Sam Brannen, Stevo Slavic, Stephane Nicoll, and Philippe Marschall.