I have been trying to get the WKND website working on my AEM instance, however it shows error in the bundles and the pages are appearing blank. I tried debugging the issue and discovered that the bundles are in installed state. It shows the below errors:
I tried updating the uber jar as well but still the error persists. The bundle is built successfully and no other errors are appearing during the build. Also while checking the pom.xml I came across this property which I'm not sure is correct for the aem 6.5 version:
I am currently using the AEM 6.5.20 version , along with service package 6.5.20 and uber jar version mentioned in pom is 6.5.20 as well. Appreciate your help everyone!!
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
In your pom.xml, the property aem.sdk.api is set to: 2023.7.12874.2023072678702512-230702 This is an AEM as a Cloud Service SDK version, not for AEM 6.5!
That means your project is compiling against AEMaaCS APIs, which are slightly different from AEM 6.5 on-premise APIs. That's why the installed bundle is missing classes and dependencies.
AEM 6.5 users should NOT use aem.sdk.api properties from the AEMaaCS SDK.
I had my doubts when I came across this property, is it possible that I remove this property and try to deploy once?
Views
Replies
Total Likes
If you're using AEM 6.5, could you please confirm which WKND codebase you're working with? If it's based on the following repository https://github.com/adobe/aem-guides-wknd/blob/main/archetype.properties then please note that it's intended for AEM as a Cloud Service, as specified in the archetype.properties file.
you can try creating AEM project using below maven archtype command as well
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=35 \
-D appTitle="My Site" \
-D appId="mysite" \
-D artifactId="mysite" \
-D groupId="com.mysite" \
-D aemVersion="6.5.2"
Views
Replies
Total Likes
You can also deploy WKND site via package that's available on github.
https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-3.2.0
Generally we do not deploy WKND with codebase, unless you are making changes and learning based on WKND code.
Views
Replies
Total Likes
I want to work on some core components in WKND for learning purposes, it's the reason why I want the codebase as well to be deployed in my local.
Views
Replies
Total Likes
Please check if core component package is installed or download from below link.
https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/versions
This is the current version which is used in my local setup, I can update this then for the core components error.
Thanks!!
Views
Replies
Total Likes
For AEM 6.5+
https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/set-up-a-...
https://github.com/adobe/aem-guides-wknd
https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/set-up-a-...
Note: Delete .m2 repository in case conflicting with different versions of bundles.
Views
Replies
Total Likes
@RekhaRa4 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes