Forums de discussion
patching-tool list-collisions
Wes Kempa, modifié il y a 8 années.
patching-tool list-collisions
New Member Publications: 24 Date d'inscription: 29/07/08 Publications récentes
After applying Liferay Portal 6.2 EE Update 2015-07-15 Portal-60 to a fresh bundle of a fresh bundle of liferay-portal-tomcat-6.2-ee-sp11-20150407182402908.zip I get the following collision:
ysl1101:patching-tool weskempa$ ./patching-tool.sh install
Cleaning up: [....................]
Installing patches: [....................]
WARNING: Plugins and patches are modifying the same files. Please run "patching-tool list-collisions" to review the possible collisions.
The patches contain new database indexes compared to the original version. Run the patching tool with the index-info parameter for more information.
Some of the plugins has an outdated version of the patched libraries. Please run the patching-tool with the update-plugins parameter to update the libraries in the deployed plugins.
The installation was successful. One patch is installed on the system.
ysl1101:patching-tool weskempa$ ./patching-tool.sh list-collisions
Listing collisions (file, plugin, patch):
html/portlet/dockbar/view_user_account.jspf, Notifications EE Portlet, portal-60
html/portlet/journal/article_toolbar.jsp, Resources Importer EE Web, portal-60
Assuming this is expected, is there anything that needs to be done in case of out of box collisions such as these?
ysl1101:patching-tool weskempa$ ./patching-tool.sh install
Cleaning up: [....................]
Installing patches: [....................]
WARNING: Plugins and patches are modifying the same files. Please run "patching-tool list-collisions" to review the possible collisions.
The patches contain new database indexes compared to the original version. Run the patching tool with the index-info parameter for more information.
Some of the plugins has an outdated version of the patched libraries. Please run the patching-tool with the update-plugins parameter to update the libraries in the deployed plugins.
The installation was successful. One patch is installed on the system.
ysl1101:patching-tool weskempa$ ./patching-tool.sh list-collisions
Listing collisions (file, plugin, patch):
html/portlet/dockbar/view_user_account.jspf, Notifications EE Portlet, portal-60
html/portlet/journal/article_toolbar.jsp, Resources Importer EE Web, portal-60
Assuming this is expected, is there anything that needs to be done in case of out of box collisions such as these?
David H Nebinger, modifié il y a 8 années.
RE: patching-tool list-coll
Liferay Legend Publications: 14919 Date d'inscription: 02/09/06 Publications récentes
As an EE customer you should actually open a LESA ticket on this...
Jorge Díaz, modifié il y a 8 années.
RE: patching-tool list-coll
Liferay Master Publications: 753 Date d'inscription: 09/01/14 Publications récentesDavid H Nebinger:
As an EE customer you should actually open a LESA ticket on this...
David, not all customers can open LESA tickets, only Gold and Platinium ones.
There are also «Limited» EE customers that cannot open tickets but they can download weekly fixpacks and access to customer knowledge base.
About the colisión question, in order to avoid issues, after installing the fixpack you should also download and install last version of Notification EE and Resource Importer EE.
In any case I think this is explained at customer knowledge base that you can access as limited customer. If you are gold or platinum, open a ticket in LESA.