Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Using quarterly release tags in my workspace

Written By

Balázs Létai

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

  • I would like to use the quarterly release tags for liferay.workspace.product and liferay.workspace.target.platform.version properties in the gradle.properties file.
    e.g. 
    liferay.workspace.product=dxp-2024.q1.1
    liferay.workspace.target.platform.version=2024.q1.1

Environment

  • Liferay Quartely releases

Resolution

  • You can update your blade CLI tool with blade update OR blade update -s (for snapshot version)
  • When you use blade version 6+ you will be able to create workspace for quarterly releases
  • blade init --list --all command can be used to list all the options.

  • Alternatively, for existing workspaces, you can change the workspace version in the settings.gradle file to use plugin version 10 or later.
dependencies {

  classpath group: "com.liferay", name: "com.liferay.gradle.plugins.workspace", version: "10.0.3"

 }

 

Additional Information

  • https://learn.liferay.com/w/dxp/liferay-development/tooling/blade-cli

 

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?