WKND tutorial | Adobe Higher Education
Skip to main content
S
shivparekh21
Level 2
May 30, 2024

WKND tutorial

  • May 30, 2024
  • 4 reacties
  • 1116 Bekeken
com.adobe.aem.wcm.seo,version=[1.1,2) -- Cannot be resolved but is not required com.adobe.aem.wcm.seo.localization,version=[1.0,2) -- Cannot be resolved but is not required com.adobe.cq.ui.wcm.commons.config,version=[1.0,2) -- Cannot be resolved com.adobe.cq.wcm.spi,version=[0.1,1) -- Cannot be resolved com.adobe.granite.ui.components,version=[1.20,2) -- Cannot be resolved com.adobe.granite.workflow,version=[1.1,2) -- Cannot be resolved com.adobe.granite.workflow.model,version=[1.2,2) -- Cannot be resolved com.day.cq.dam.scene7.api.constants,version=[2.11,3) -- Cannot be resolved com.day.cq.search,version=[1.4,2) -- Cannot be resolved com.day.cq.wcm.api,version=[1.29,2) -- Cannot be resolved com.day.cq.wcm.commons,version=[5.9,6) -- Cannot be resolved com.fasterxml.jackson.annotation,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.core,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind.annotation,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind.introspect,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind.module,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind.ser,version=[2.11,3) -- Cannot be resolved com.fasterxml.jackson.databind.ser.std,version=[2.11,3) -- Cannot be resolved javax.annotation.meta -- Cannot be resolved but is not required javax.xml.bind,version=[2.3,3) -- Cannot be resolved javax.xml.bind.annotation,version=[2.3,3) -- Cannot be resolved org.apache.commons.codec.digest,version=[1.14,2) -- Cannot be resolved org.apache.commons.lang3,version=[3.12,4) -- Cannot be resolved org.apache.commons.lang3.tuple,version=[3.12,4) -- Cannot be resolved org.apache.jackrabbit.util,version=[2.5,3) -- Cannot be resolved org.apache.sling.api.resource,version=[2.12,3) -- Cannot be resolved org.apache.sling.api.scripting,version=[2.5,3) -- Cannot be resolved org.apache.sling.api.servlets,version=[2.3,3) -- Cannot be resolved
 


D:\code\aem-guides-wknd>java -version
java version "11.0.23" 2024-04-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.23+7-LTS-222)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.23+7-LTS-222, mixed mode)

 

 

D:\code\aem-guides-wknd>mvn -v
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: D:\apache-maven-3.9.6
Java version: 11.0.23, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-11
Default locale: en_IN, platform encoding: Cp1252
OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"

 

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=48" "-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.0"

 

mvn clean install -PautoInstallSinglePackage -Pclassic

 

 

WKND en page is appearing blank.

Is there anything I am doing wrong here?? java version 11 is compatible too

Er kunnen geen reacties meer worden geplaatst op dit onderwerp.

4 reacties

M
mike2828
May 30, 2024

Hi @shivparekh21 , I could see that you have created a new maven project instead of building an existing https://github.com/adobe/aem-guides-wknd project, kindly clone the project again and use the below commands to deploy to the instance. 

$ mvn clean install -PautoInstallPackage

    EstebanBustamante
    Community Advisor and Adobe Champion
    EstebanBustamanteCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 30, 2024

    Hi @shivparekh21 

     

    Most likely you are missing an SP in your AEM instance, please review the system requirements here: https://github.com/adobe/aem-guides-wknd?tab=readme-ov-file#system-requirements and make sure you are using the correct version with the respective SP.

    Hope this helps

    Esteban Bustamante
      S
      shivparekh21Auteur
      Level 2
      June 11, 2024

      Do I need service package when i am deploying it to server??

       

      HrishikeshKagne
      Community Advisor
      HrishikeshKagneCommunity Advisor
      Community Advisor
      June 2, 2024

      Hi @shivparekh21 ,

      It looks like you're encountering dependency resolution issues when building the WKND project in AEM 6.5 using Maven. These errors indicate that certain OSGi dependencies are not being resolved during the build process.

      Here are the steps to troubleshoot and resolve these issues:

      1. Check Dependencies and Repositories

      Ensure that the pom.xml of your project contains the correct dependencies and repositories for resolving the required bundles.

      a. Verify Repositories

      Make sure you have the following repositories configured in your pom.xml:

       

      <repositories> <repository> <id>adobe-public-releases</id> <url>https://repo.adobe.com/nexus/content/groups/public/</url> </repository> <repository> <id>central</id> <url>https://repo.maven.apache.org/maven2</url> </repository> </repositories>

       

      b. Verify Dependencies

      Ensure that the dependencies for the required packages are listed in your core/pom.xml or all/pom.xml:

       

      <dependencies> <!-- Example dependencies, adjust versions as needed --> <dependency> <groupId>com.adobe.aem</groupId> <artifactId>aem-sdk-api</artifactId> <version>2021.10.5455.20211012T100432Z-210900</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.adobe.cq</groupId> <artifactId>cq-wcm-api</artifactId> <version>6.5.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-core</artifactId> <version>2.11.3</version> </dependency> <!-- Add other required dependencies similarly --> </dependencies>

       

      2. Ensure Proper Maven Profiles

      Ensure that you are using the correct Maven profiles during the build. For AEM 6.5, the classic profile should be sufficient, but you might need to adjust the build profiles.

       

      mvn clean install -PautoInstallSinglePackage -Pclassic

       

      3. Verify OSGi Bundle Versions

      Check if the specific versions of the required OSGi bundles are available in the Adobe repository. If they are not, you might need to adjust the versions in your pom.xml.

      4. Update and Synchronize Dependencies

      Sometimes, updating the project and synchronizing dependencies can resolve version conflicts:

       

      mvn clean install -U

       

      5. Check AEM Instance and Logs

      • Ensure your AEM instance (Author/Publish) is running and accessible.
      • Check the AEM error logs (/crx-quickstart/logs/error.log) for any deployment or runtime issues.

      Example core/pom.xml Configuration

      Here’s an example configuration snippet for core/pom.xml:

       

      <project> <!-- Other configurations --> <dependencies> <dependency> <groupId>com.adobe.aem</groupId> <artifactId>aem-sdk-api</artifactId> <version>2021.10.5455.20211012T100432Z-210900</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.adobe.cq</groupId> <artifactId>cq-wcm-api</artifactId> <version>6.5.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-core</artifactId> <version>2.11.3</version> </dependency> <!-- Add other dependencies similarly --> </dependencies> <repositories> <repository> <id>adobe-public-releases</id> <url>https://repo.adobe.com/nexus/content/groups/public/</url> </repository> <repository> <id>central</id> <url>https://repo.maven.apache.org/maven2</url> </repository> </repositories> <!-- Other configurations --> </project>

       

      Conclusion

      By ensuring that the correct dependencies and repositories are configured in your pom.xml files, you should be able to resolve the issues with missing packages and OSGi dependencies. If problems persist, review the error logs for more specific details on the root cause and adjust your project configuration accordingly.

      Hrishikesh Kagane
      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      June 4, 2024

      @shivparekh21 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 have found out solution yourself, please share it with the community.

      Kautuk Sahni
      ForumvoorwaardenAccessibility statement

      Loading footer...