Don't allow a plugin that is older to replace a newer version of the plugin
Description
None
Activity
Show:

Luyang Tan July 31, 2012 at 10:43 PM

Michael Saechang July 25, 2012 at 11:04 AMEdited
Committed on:
Portal 6.1.x CE GIT ID: 326a184221a2e24b739a34f0428b61fcbdcd9372.
Portal 6.2.x GIT ID: 80b75f5e1ec652ef447249ecf3fb28b394a96685.
Fixed
Details
Assignee
Luyang TanLuyang Tan(Deactivated)Reporter
Brian ChanBrian ChanLabels
Branch Version/s
6.1.xBackported to Branch
CommittedFix Priority
4Components
Affects versions
Priority
Medium
Details
Details
Assignee

Reporter

Labels
Branch Version/s
6.1.x
Backported to Branch
Committed
Fix Priority
4
Components
Affects versions
Priority
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created July 24, 2012 at 4:45 PM
Updated June 24, 2023 at 3:49 PM
Resolved July 24, 2012 at 4:46 PM
PASSED Manual Testing using the following steps:
1. Startup liferay, deploy a portlet.
2. Deploy the same portlet but older than the previous one.
Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: ba89e19182c2b72aa89a560c061160b11b01aa24.
I can still deploy the portlet successfully.
Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GIT ID: a4e4deb86cd53686a028af844196c2abce0389e7.
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 1b34701133317b83ff8bf3193d8789da9506b9b8.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 49b16a7cfe7d0bcd089320c8fb5ae2fa188840bb.
I will see the message in the console: Not updating portlet because version XXX is newer than version XXX.