This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. « Back to Upgrade Instructions
Upgrade Process Customization
Table of Contents [-]
If you're looking for the release numbers and wondering how the upgrade classes are run, this is the place.
In portal.properties, there a section called Upgrade:
##
## Upgrade
##
#
# Input a list of comma delimited class names that implement
# com.liferay.portal.upgrade.UpgradeProcess. These classes will run on
# startup to upgrade older data to match with the latest version.
#
upgrade.processes=com.liferay.portal.upgrade.UpgradeProcess_**XYZ**This contains a list of classes that will be run by StartupAction.
These classes all extend the abstract class UpgradeProcess.
Within these classes, they are assigned a release build number in the getThreshold() method.
StartupAction compares this number against a number stored in the database.
This number is stored in the buildNumber column of the Release_ table.
If the stored number in the database is less than the number in the class, than the upgrade will run.
29149 Views
