掲示板
the best way to undeploy
9年前 に Soukaina HAJI によって更新されました。
the best way to undeploy
Regular Member 投稿: 195 参加年月日: 14/06/17 最新の投稿
what is the best way to undeploy a project ? is just deleting the folder from webapps is enough ? because the files overrided doesnt change to the default ?
thank you
thank you
9年前 に David H Nebinger によって更新されました。
RE: the best way to undeploy
Liferay Legend 投稿: 14919 参加年月日: 06/09/02 最新の投稿
That will work for everything but an EXT plugin. You don't undeploy an EXT plugin, you revert to a clean bundle and start over.
9年前 に Jack Bakker によって更新されました。
RE: the best way to undeploy
Liferay Master 投稿: 978 参加年月日: 10/01/03 最新の投稿Soukaina HAJI:
what is the best way to undeploy a project ? is just deleting the folder from webapps is enough ? because the files overrided doesnt change to the default ?
thank you
Vijay's question is useful to narrow in to help
Soukaina, I think you mean plugin not project ?
ext and hook plugins might need more attention than say a portlet plugin ; it is about understanding dependencies
cleaning temp and work in tomcat might be needed too
9年前 に Soukaina HAJI によって更新されました。
RE: the best way to undeploy (回答)
Regular Member 投稿: 195 参加年月日: 14/06/17 最新の投稿
The best way to undeploy a hook plugin is to override all the jsp files in the plugin with a fresh jsp file ( not modified ) and then remove it from webapps,
because hook plugin take the files from the plugin and override it inside ROOT ...
because hook plugin take the files from the plugin and override it inside ROOT ...
9年前 に David H Nebinger によって更新されました。
RE: the best way to undeploy
Liferay Legend 投稿: 14919 参加年月日: 06/09/02 最新の投稿
That's totally unnecessary.
Yes a hook copies the jsp to ROOT, but when you look in the ROOT where the jsp was placed, you'll see original.portal.jsp right next to your changed orginal.jsp. When you undeploy the hook that file is put back in place.
You get into trouble when you deploy multiple hooks for the same file; I'm not sure the original.portal.jsp is still the portal's jsp.
But you shouldn't be hooking the same jsp files in your hooks anyway.
Yes a hook copies the jsp to ROOT, but when you look in the ROOT where the jsp was placed, you'll see original.portal.jsp right next to your changed orginal.jsp. When you undeploy the hook that file is put back in place.
You get into trouble when you deploy multiple hooks for the same file; I'm not sure the original.portal.jsp is still the portal's jsp.
But you shouldn't be hooking the same jsp files in your hooks anyway.