Navigate to following location to delete only those jar files mentioned below:ĥ. Navigate to /webapps/ROOT/WEB-INF folder and delete the following files only:Ĥ. Delete the folder sample-ext from "webapps" folderģ. So following are some steps which will help in un-deploying the ext-plugin from the server:Īssuming the name of ext-plugin is "sample-ext"Ģ. One more reason this command is used more frequently is that people find un-deploying ext-plugin difficult. So one should use SSH for Linux servers or RDC for Windows Server to deploy the war files on the server.Īs we all know that ext-plugin is still not 100% hot deployable and just because of this reason developers tend to use ant direct-deploy command to deploy ext on the servers. So if the customer uses Liferay 6.x version then best practice is NEVER keep source code on servers. The major reason why ext was moved to plugins was that in earlier versions of Liferay code had to be placed on the server to deploy ext, which was a major concern from potential customers. Since Liferay 6.0 extension environment was moved to plugins, it transformed the way core functionalities can be overridden, but there are some best practices which justifies why ext development was moved to plugins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |