RE: Liferay Portal 7.4 GA120 - How to set up a working workspace ?

thumbnail
Ivano Carrara, modified 1 Year ago. Expert Posts: 350 Join Date: 7/3/05 Recent Posts

Starting 7.4.3.120-ga120 it's impossible to set up a workspace that works, including the ability to deploy a module and autocomplete while writing code.

 

Executing Gradle tasks (build, deploy, etc.) for an "example" Service Builder module I obtain the below error:
-------------------------------------------
Execution failed for task ':modules:example:example-api:compileJava'.
> Could not resolve all files for configuration ':modules:example:example-api:compileClasspath'.
   > Could not find com.liferay.portal:release.portal.api:.
     Required by: project :modules:example:example-api
-------------------------------------------

It's clear that it doesn't find release.portal.api in the classpath.

 

Here is my setup:

- java version "11.0.17" 2022-10-18 LTS
- javac 11.0.17

 

-----> gradle-wrapper.properties:
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-bin.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

 

-----> gradle.properties:
liferay.workspace.bundle.dist.include.metadata=true
liferay.workspace.modules.dir=modules
liferay.workspace.themes.dir=themes
liferay.workspace.wars.dir=modules
microsoft.translator.subscription.key=
liferay.workspace.product=portal-7.4-ga120
​​​​​​​liferay.workspace.target.platform.version=7.4.3.120
target.platform.index.sources=true

 

-----> settings.gradle:
buildscript {
    dependencies {
        classpath group: "com.liferay", name: "com.liferay.gradle.plugins.workspace", version: "latest.release"
    }

    repositories {
        mavenLocal()

        maven {
            url "https://repository-cdn.liferay.com/nexus/content/groups/public"
        }
    }
}

apply plugin: "com.liferay.workspace"
---------------------------------------------

 

Please what do you think is further needed to check to get a Liferay Portal 7.4 GA120 workspace with autocomplete and the ability to deploy a module?

 

Thank you in advance for any help.

Jamie Sammons, modified 1 Year ago. New Member Post: 1 Join Date: 3/13/24 Recent Posts

The release process is currently broken. They managed to "somewhat fix" the DXP version after a lot of complainment but it seems, that the CE version ist also broken. I have checked https://releases.liferay.com/releases.json to see, if it's related to the liferay.workspace.product version in the Liferay Workspaces gradle.properties. Seems like portal-7.4-ga120 exists but shows "DXP" in its name, for whatever reason. The last version, which works for me is portal-7.4-ga112.

 

@Liferay: please fix your stuff!

Jamie Sammons, modified 1 Year ago. New Member Posts: 6 Join Date: 3/3/20 Recent Posts

Hi,
Did you get the working workspcae of Liferay 7.4-ga120 ? or still you have issue with the new version? Please share your experience.

thumbnail
Ivano Carrara, modified 1 Year ago. Expert Posts: 350 Join Date: 7/3/05 Recent Posts

Has anyone put the Liferay workspace 7.4 GA120 to work?

David H Nebinger replying to my comment to their Blog article wrote:

"In the mean time, if you just tack on the version in your build.gradle files for the target version, the builds will be successful."

Unfortunately I didn't understand what he meant.

What and where should I put what he suggest?

Actually my gradle.properties content is the below:

liferay.workspace.bundle.dist.include.metadata=true
liferay.workspace.modules.dir=modules
liferay.workspace.themes.dir=themes
liferay.workspace.wars.dir=modules
microsoft.translator.subscription.key=
liferay.workspace.product=portal-7.4-ga120
liferay.workspace.target.platform.version=7.4.3.120
target.platform.index.sources=true
​​​​​​​

Thanks in advance for any comment.

thumbnail
Ivano Carrara, modified 1 Year ago. Expert Posts: 350 Join Date: 7/3/05 Recent Posts

Is anyone using the  Liferay 7.4-ga120 workspace?

There seems to be an easy solution but no one seems to want to suggest it.

The solution to this issue seems to be the best kept secret in the Liferay world.

Thanks in advance for any input on this.

thumbnail
Russell Bohl, modified 1 Year ago. Expert Posts: 308 Join Date: 2/13/13 Recent Posts

        Hi Ivano, the workaround is to specify the artifact version in build.gradle:

dependencies {
	compileOnly group: "com.liferay.portal", name: "release.portal.api", version: "7.4.3.120"
}

 

thumbnail
Ivano Carrara, modified 1 Year ago. Expert Posts: 350 Join Date: 7/3/05 Recent Posts

Dear Russell, thank you very very very much :-)