When we create Liferay applications (such as Portlet,theme) with Maven, we often have a version choice, as shown in the figure:
The default show's last version of Archetype is selected, at which point we can only display the latest version of archetype, if we use the latest version of archetype development application, then eventually when the application deployed to the lower version of the container ( For example, the Liferay server version of our goal is 6.1.0), the following error occurs:
Copying portlets For/app/liferay/ri/liferay-portal-6.1.0-ce-ga1/deploy/paas_integration_portlet.war
03:11:17,971 ERROR [autodeploydir:197] com.liferay.portal.kernel.deploy.auto.AutoDeployException: Com.liferay.portal.kernel.deploy.auto.AutoDeployException:paas_integration_portlet.war does not support this Version of Liferay
com.liferay.portal.kernel.deploy.auto.AutoDeployException: Com.liferay.portal.kernel.deploy.auto.AutoDeployException:paas_integration_portlet.war does not support this Version of Liferay
Error Analysis:
Obviously, the error message is the Portletautodeploylistener of the lower version (6.1.0) Liferay container when the ${liferay.home}/deploy directory is detected with a portlet application that our MAVEN deploys, It cannot be processed because it sees a portlet application version higher than the Liferay container's own processing capacity.