Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Patching Tool 'support-info' command

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Trying to run the 'support-info' command using the patching tool, but nothing happens. But there is no output, and there is no error.

  • How can users find out about modules?

Environment

  • Liferay DXP Patching Tool 3.0.19+

Resolution

  • The 'support-info' command has been removed from patching tool versions 3.0.19+, thus users have to run the below commands separately to obtain the details of the specific environment.
    • “info”
      “modules-info”
  • To output the patching information for the specific environment, the following command must be utilized from the patching-tool folder:  patching-tool.bat info or patching-tool.bat modules-info
  • Use the following command to pipe the patching tool information directly to a .txt file:  patching-tool.bat modules-info > patchinfo.txt

Additional Information

  • All patching-tool commands must be executed from the LIFERAY_HOME/patching-tool directory​
  • For Ubuntu:    ./patching-tool.sh
  • For Windows: patching-tool.bat
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?