Closed Rojkumar2306 closed 2 years ago
Hi @Rojkumar2306 a few follow ups:
classic
variation that is intended to be installed on 6.5 environmentsHi @Rojkumar2306 a few follow ups:
- what version of AEM are you using, is this 6.5?
- Also what Service Pack do you have?
- What version of WKND did you install? There is a
classic
variation that is intended to be installed on 6.5 environments
Yes i am using 6.5. Whenever i am trying to extract zip files(aem-guides-wknd-main.zip) i am getting errors like error 0x80010135. path too long. and... could u please clarify that 1.i should install "aem- guides-wknd-all-1.1.0.-classic.zip" and then i should install "aem-guides-wknd-main.zip". thats what i am doing..please guide me if gng in wrng direction as i am beginner. **my maven version 3.8.5 **aem 6.5 provided by my organization which i am wrkng now. *****should i prefer Java version 11 or 1.8????
help me out plssss...its killing my time
i tried to validate the classic package. This is what i got.. if i proceed to install anyway, We-retail & wknd-sites wont be active. what should i do now???????????
Validate Package: [/etc/packages/com.adobe.aem.guides/aem-guides-wknd.all-1.1.0.zip]() Thu Apr 21 2022 11:06:56 GMT+0530 (India Standard Time)
Validating content package
5 unsatisfied OSGi package imports in 2 bundles.
Following 2 bundles will go from 'Active' to 'Installed' state if you install this content package.
5 unsatisfied OSGi package imports. No overlay rebase warnings. No ACL warnings.
Package validated in 1ms.
running into the same issue hopefully this helps. This is the console log and it's showing that is's unable to resolve a few bundles.
Thanks @mthomas46. Apologies @Rojkumar2306 I didn't see your response. I think the issues are related to the lack of Service Pack installed on the target 6.5 environments.
The latest release of WKND for AEM 6.5 requires a minimum Service Pack 10 to be installed. If this is a fresh environment install the latest service pack which is 12:
for @mthomas46 it looks like you generated a new project using the AEM Project Archetype? I'm not sure if that is the case but I see that the version you have is 0.0.1-SNAPSHOT. If this is the case ensure that when generating the project you specify the version of AEM you are using. So for Service Pack 10 you would generate a new project like so:
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="WKND Sites Project" \
-D appId="wknd" \
-D groupId="com.adobe.aem.guides" \
-D artifactId="aem-guides-wknd" \
-D package="com.adobe.aem.guides.wknd" \
-D version="0.0.1-SNAPSHOT" \
-D aemVersion="6.5.10"
And also ensure that Service Pack 10 is installed on the target AEM 6.5 environment.
@godanny86 so i copied the project repo from the component-basics-start branch. It seems like the documentation or branch for the tutorial is a little out of date. i'm using service pack 8 so thats probably the reason, i'll try grabbing 12.
hey @mthomas46 the tutorial specifies 6.5.10 as a minimum version: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/overview.html?lang=en#local-dev-environment. Is there another place where you see SP 8 referenced?
@godanny86 the link to the service pack does not seem to work with a personal account. I'll have to ask a coworker to get it for me. thanks for the help.
I've upgraded to SP12 and it still is unable to resolve the following bundles on a fresh install org.apache.sling.api.request,version=[2.6,3) -- Cannot be resolved org.apache.sling.api.resource,version=[2.13,3) -- Cannot be resolved
Thanks @mthomas46 i'll try and reproduce on my end. Remind me, what branch are you working with, is it: https://github.com/adobe/aem-guides-wknd/tree/tutorial/component-basics-start ?
Thanks @mthomas46 i'll try and reproduce on my end. Remind me, what branch are you working with, is it: https://github.com/adobe/aem-guides-wknd/tree/tutorial/component-basics-start ?
component basic start
@godanny86 any update on this?
Hey @mthomas46 i wasn't able to reproduce it. Are you using the -Pclassic
profile to build?
mvn clean install -PautoInstallSinglePackage -Pclassic
Hey @mthomas46 i wasn't able to reproduce it. Are you using the
-Pclassic
profile to build?mvn clean install -PautoInstallSinglePackage -Pclassic
i'll give that a shot
Closing this as because of no further updates, if the issue persists please reopen.
after installing bundles, in http://localhost:4502/system/console/bundles "wknd-sites" & "We-Retail" are showing as installed instead of active. Unable to see content on edit pages.