Legacy Knowledge Base
Published Sep. 10, 2025

Why does my portlet not have a version number after it is deployed?

Written By

Nathan Roberts

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

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

Issue

  • Deploying a .war portlet through the /liferay_home/deploy folder leads to the deployed portlet not having a version number in its file name.

Environment

  • Liferay DXP 7.0 de-33+
  • Liferay DXP 7.1

Resolution

  • A fix implemented in de-33 addressed a potential issue were multiple copies of the same portlet could end up deployed at the same time. Part of this fix was to remove extensions to portlet file names, ensuring that only one copy of a portlet will be deployed.

Additional Information

  • A workaround was found that results in a deployed .war portlet retaining a version number. The workaround is to add a copy of the version/snapshot file name extension to the file's name. An important note, as this workaround effectively bypasses the fix that was implemented, there is the potential for multiple copies of the same portlet, though of different versions, to be deployed on the same server. Please use this workaround at your discretion.

    Example:
    When de-33+ is installed and portlet-1.0.war is deployed it is renamed as portlet.war. Using the workaround the file can be renamed to portlet-1.0-1.0.war which when deployed is renamed to portlet-1.0.war.
Did this article resolve your issue ?

Legacy Knowledge Base