Ivano Carrara 5 Days Ago - Edited Dear David your new article about dev setup is awesome but still in my case is a nigthmare. Still 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 Possible solution: - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html ------------------------------------------- (Please note that anyway in the previous 7.4.3.112 version the "liferay.workspace.target.platform.version=7.4.3.112" statement in "gradle.properties" is mandatory to obtain autocomplete.) Before to restart the setup I cleared all cache, temp, etc folders. 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 target.platform.index.sources=true - settings.gradle: buildscript { dependencies { classpath group: "com.liferay", name: "com.liferay.gradle.plugins.workspace", version: "10.1.3" } repositories { mavenLocal() maven { url "https://repository-cdn.liferay.com/nexus/content/groups/public" } } } apply plugin: "com.liferay.workspace" --------------------------------------------- After the setup the IDE and Gradle downloaded all dipendencies and artifacts from repositories. Of course I'm sure it is my fault but I can't understand it - all things are the same as your articles. Still the autocomplete and the ability to deploy a module is missing in my 7.4.3.120 version dev environment. Please sign in to reply. Reply as... Cancel Ivano Carrara Ivano Carrara 5 Days Ago - Edited Note: Starting 7.4.3.101 version the "liferay.workspace.target.platform.version=7.4.3.101" statement in "gradle.properties" is mandatory to obtain autocomplete. Please sign in to reply. Reply as... Cancel David H Nebinger Ivano Carrara 5 Days Ago - Edited Specifying the target version explicitly is an even better way to use the version rather than tacking onto the build.gradle files... Please sign in to reply. Reply as... Cancel David H Nebinger Ivano Carrara 5 Days Ago - Edited Hey Ivano! We've been having some issues with the BOMs and property details, and you're hitting the problem shared by many. The portion of the error which shows the artifact, "com.liferay.portal:release.portal.api:.", it doesn't have a version tacked on the end, just a period. That's an indicator that it is not able to derive the version to use from the target platform tied to the workspace version you've defined in gradle.properties... Can you share what your gradle.properties workspace is? I'll go back to the team and get them to research... 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. Please sign in to reply. Reply as... Cancel Ivano Carrara David H Nebinger 5 Days Ago - Edited Hello David! Thank you for the explanation of the original issue. Here is the content of my build.gradle: --- 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 --- As you can see I already specified the version but still the "com.liferay.portal:release.portal.api:." stay without the version number. Also I manually tried to insert a version number in IntelliJ IDEA 2024.1.4 ---> Project Structure ---> Project Settings ---> Libraries but the IDE clears the version field. Please sign in to reply. Reply as... Cancel
Ivano Carrara Ivano Carrara 5 Days Ago - Edited Note: Starting 7.4.3.101 version the "liferay.workspace.target.platform.version=7.4.3.101" statement in "gradle.properties" is mandatory to obtain autocomplete. Please sign in to reply. Reply as... Cancel David H Nebinger Ivano Carrara 5 Days Ago - Edited Specifying the target version explicitly is an even better way to use the version rather than tacking onto the build.gradle files... Please sign in to reply. Reply as... Cancel
David H Nebinger Ivano Carrara 5 Days Ago - Edited Specifying the target version explicitly is an even better way to use the version rather than tacking onto the build.gradle files... Please sign in to reply. Reply as... Cancel
David H Nebinger Ivano Carrara 5 Days Ago - Edited Hey Ivano! We've been having some issues with the BOMs and property details, and you're hitting the problem shared by many. The portion of the error which shows the artifact, "com.liferay.portal:release.portal.api:.", it doesn't have a version tacked on the end, just a period. That's an indicator that it is not able to derive the version to use from the target platform tied to the workspace version you've defined in gradle.properties... Can you share what your gradle.properties workspace is? I'll go back to the team and get them to research... 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. Please sign in to reply. Reply as... Cancel Ivano Carrara David H Nebinger 5 Days Ago - Edited Hello David! Thank you for the explanation of the original issue. Here is the content of my build.gradle: --- 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 --- As you can see I already specified the version but still the "com.liferay.portal:release.portal.api:." stay without the version number. Also I manually tried to insert a version number in IntelliJ IDEA 2024.1.4 ---> Project Structure ---> Project Settings ---> Libraries but the IDE clears the version field. Please sign in to reply. Reply as... Cancel
Ivano Carrara David H Nebinger 5 Days Ago - Edited Hello David! Thank you for the explanation of the original issue. Here is the content of my build.gradle: --- 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 --- As you can see I already specified the version but still the "com.liferay.portal:release.portal.api:." stay without the version number. Also I manually tried to insert a version number in IntelliJ IDEA 2024.1.4 ---> Project Structure ---> Project Settings ---> Libraries but the IDE clears the version field. Please sign in to reply. Reply as... Cancel