Since the release of the last Patching Tool v20, we have been busy implementing new improvements that will enhance the user experience as well as the Support engineers’ ability to assist users. Starting with version 21, the Patching Tool will log the installed patch levels of your portal instance so that Support engineers can easily determine the chronological patching history by viewing the support-info command output.
Resolution
The Service Pack detection is now available behind a proxy server. The configuration for the proxy authentication in the Patching Tool’s configuration file can be set to the following:
### Proxy # HTTPS Proxy
proxy.https.host=192.168.211.39 proxy.https.port=808 proxy.https.user=user proxy.https.password=password # SOCKS Proxy
# proxy.socks.host=192.168.211.39 # proxy.socks.port=1080 # proxy.socks.user=user # proxy.socks.password=password
In the past, issues could be encountered with the Patching Tool when the portal was not completely shut down. The Patching Tool v21 will now handle this situation by checking if the portal files have been overridden by a plugin and then patching only the original files in order to avoid conflicts. Please note that it is still important to allow the portal to shut down properly so that the hooks can unregister successfully.
Reference: Installing a Patch Without Correctly Shutting Down Liferay Portal Corrupts the Portal Files
Other minor bug fixes and updates include:
- In source mode, after a user reverts a patch with new files, the older files will be removedJAR files can be replaced in source mode
- Support has been added for patching optional files
- Download-all-latest(-src) command will not download old fixpacks
- Deleted classes are removed after patching
- Increased accuracy of the progress bar’s indication for SourceProducts
Download
To download and obtain more information on the latest version of the patching tool, please visit the Patching Tool page on the Customer Portal.