Legacy Knowledge Base
Published Jul. 2, 2025

How do I automatically upgrade a 6.2 Maven theme to be a 7.x Maven theme?

Written By

Alfonso Crisci

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.

NOTE: This article is an INTERNAL article and is not visible to customers, currently. Please only link this article in internal comments, but not public comments.

Issue

  • How do I automatically upgrade a 6.2 Maven theme to be a 7.x Maven theme?

Environment

  • Liferay DXP 7.0+

Resolution

  • There is no automated process to perform the upgrade by taking advantage of the Theme Generator capabilities, below is an alternative way to complete the requirement:

    Blade can be used to convert the 6.2 theme to a gulp project. Here's an article for that: Upgrading Your Theme from Liferay Portal 7.0 to 7.2

    Once the blade convert command finishes and the project is converted to gulp, it will be up to the developers to fix up their theme to make sure it deploys on 7.2
  • Into specific, here are the steps:
  1. blade create -t newTheme -v 7.2 -b maven
  2. Copy over everything in src/main/webapp from the 6.2 theme to the newly created theme
  3. mvn verify (this should build the theme) otherwise, it should build the same way as in 6.2

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base