CODEWITHSUNDEEP
javamavenadobeaemvenia
Script Host
Script Host

Reputation: 922

AEM 6.5 Venia - Corevenia.core in console throwing error

I am very new to AEM 6.5, So basically I set up AEM in Ubuntu 20. I set up the requirement for AEM and its working fine, Next, when I thought of customizing the theme venia which I cloned from the GitHub link https://github.com/adobe/aem-cif-guides-venia, as I have started as per GitHub steps first I ran

mvn clean install -PautoInstallSinglePackage,cloud

after that, the BUILD was a success, but when referring to the console the following error is showing as attached, and list

com.adobe.cq.commerce.core.components.models.common,version=[1.8,2) -- Cannot be resolved
com.adobe.cq.commerce.core.components.models.productteaser,version=[2.0,3) -- Cannot be resolved
com.adobe.cq.commerce.core.components.models.retriever,version=[1.11,2) -- Cannot be resolved

enter image description here

I could not find any solution for the error. Any Help will be appreciated !!

Upvotes: 1

Views: 340

Answers (2)

Daniel Platon
Daniel Platon

Reputation: 603

Do not install Venia on AEM 6.4 using the cloud profile. You should install it using the classic profile: mvn clean install -PautoInstallSinglePackage,classic

From the README:

* classic: this profile is for Abobe Managed Services (AMS) or on-premise deployments.

Also, I'm not sure that the latest Venia sample app is supported on AEM 6.4.4.0

Upvotes: 2

Florian Salihovic
Florian Salihovic

Reputation: 3961

Without having looked too much into aem-cif-guides-venia, I assume the build was successful as the dependencies are defined as run time dependencies. In other words: the build does not build the packages and bundles together with the required dependencies, but expects the dependencies to be available in the running AEM instance.

  1. You need to check the bundle versions of the red marked dependencies. There might be a version mismatched or the instance had issues during startup. I suspect this to be the root cause.
  2. You need to check the error log for further information.

If it is a bundle version issue, you could go an fork aem-cif-guides-venia and adjust the versions and redeploy.

I know this is not the goto answer but AEM, and OSGI specifically, is a highly dynamic application and troubleshooting is quite tricky at the beginning.

Upvotes: 0

Related Questions