WKND Tutorial - Project Setup | AEM Community Blog Seeding | Community
Skip to main content
kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
May 4, 2020

WKND Tutorial - Project Setup | AEM Community Blog Seeding

  • May 4, 2020
  • 1 reply
  • 12559 views

BlogImage.jpg

WKND Tutorial - Project Setup by Adobe Docs

Abstract

This tutorial covers the creation of a Maven Multi Module Project to manage the code and configurations for an Adobe Experience Manager Site.

Prerequisites
Review the required tooling and instructions for setting up a local development environment . Ensure that you have a fresh instance of Adobe Experience Manager available locally and that no additional sample/demo packages have been installed (other than required Service Packs).

Read Full Blog

WKND Tutorial - Project Setup

Q&A

Please use this thread to ask the related questions.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    Blaiirrr
    Blaiirrr
    Level 2
    May 4, 2020

    Hi - total noob here (and hope I'm asking this question in the right place).  Just working my way though the WKND setup and am getting a Build Error when running "mvn -PautoInstallBundle clean install" in the /core folder:

    [ERROR] Failed to execute goal on project aem-guides-wknd.core: Could not resolve dependencies for project com.adobe.aem.guides:aem-guides-wknd.core:jar:0.0.2:The following artifacts could not be resolved: com.adobe.aem:uber-jar:jar:apis:6.5.0, org.apache.commons:commons-imaging:jar:1.0-R1534292, com.day.commons:day-commons-gfx:jar:2.1.28: Could not find artifact com.adobe.aem:uber-jar:jar:apis:6.5.0 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

    Any ideas how I can fix this?

      P
      peterv18157064
      May 5, 2020

      Hi Blairrr,

       

      did you register the Adobe public repo as explained below step two of the tutorial (Verify that the adobe-public profile is active by running the following command...)?

       

      You should check that

      mvn help:effective-settings

       lists the profile 'adobe-public' and if it doesn't change your maven settings according to this documentation:

      Set up a Local AEM Development Environment

       

      Cheers

        S
        SurbhiChhabra
        December 8, 2021

        Well - color me stupid!  It looks like I did miss a step because I didn't even have a .m2/settings.xml file.  I've created it as instructed and now my build errors are no more 🙂, and I see my Hello World component updates too.  Many thanks for your responses, and I apologize for wasting your time.


        Hi,

         

        you definitely saved my time, had the same issue, this thread helped me to understand quickly where the issue was, got the settings file, all works well now.

        Cheers!

          Terms & ConditionsAccessibility statement

          Loading footer...