Installing Archived Modules From Liferay's Public Repository

This article is a how-to guide for locating, downloading and installing modules from Liferay’s public repository. Installing modules directly from Liferay’s public repository should be done if the module or application has been deprecated, archived or otherwise not distributed with the product. Version updates or code modifications to modules included with Digital Experience Platform (DXP) should be performed using Liferay fix packs and the patching tool.


  1. Visit the Nexus Repository Manager
  2. Determine the name of the module. If the module was bundled with DXP, the name of the module is often listed in the deprecation documentation. If the module was released as a marketplace app, the name can be determined by opening the lpkg.
  3. Browse or search the liferay-public-releases repository for the module name.
  4. Select the module folder and expand the highest version folder
  5. In the right-hand panel select the artifact tab to view more details about the uploaded date of the module.
  6. Using the uploaded date find the module version which is closest, but prior to the release date of the GA or SP on which these modules will be deployed.
    1. For instance, if the module will be deployed using DXP 7.0 SP6 which was released on 2017-10-19, version 2.0.4 of the module was uploaded on 2017-10-11.
    2. To determine a GA or SP release date, please reference the Post Date of the asset listed on the Help Center Downloads page.
  7. Most features or apps will have require several modules such as the web, api, or service module. Depending on the apps, more modules could be required. Repeat step 6 for these other modules.
    1. The versions of api, service, and web modules are not linked, meaning, if there was a module, the version closest, but prior to the release date of DXP 7.0 SP6 would not necessarily be 2.0.4.
  8. Once downloaded, copy all of the necessary modules to the deploy folder of the DXP instance.
    1. Please ensure that the modules are deployed to all nodes of a cluster.

Additional Information

Was this article helpful?
1 out of 1 found this helpful