Highlighted

WKND Tutorial - Project Setup | AEM Community Blog Seeding

kautuk_sahni

Community Manager

04-05-2020

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.

Adobe Experience Manager as a Cloud Service AEM AEMACS AEMCS AEMIBlogSeeding Experience Manager

Replies

Highlighted

Blaiirrr

04-05-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?

Highlighted

peterv18157064

05-05-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

Highlighted

Blaiirrr

05-05-2020

Yes - all steps up to that point went well. My response is a little different to the documentation, but 'adobe-public' is there.

<settings xmlns="http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd">
  <localRepository>C:\Users\bmackint\.m2\repository</localRepository>
  <profiles>
    <profile>
      <activation />
      <properties>
        <releaseRepository-Id>adobe-public-releases</releaseRepository-Id>
        <releaseRepository-Name>Adobe Public Releases</releaseRepository-Name>
        <releaseRepository-URL>https://repo.adobe.com/nexus/content/groups/public</releaseRepository-URL>
      </properties>
      <repositories>
        <repository>
          <releases>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
          <id>adobe-public-releases</id>
          <name>Adobe Public Repository</name>
          <url>https://repo.adobe.com/nexus/content/groups/public</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <releases>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
          <id>adobe-public-releases</id>
          <name>Adobe Public Repository</name>
          <url>https://repo.adobe.com/nexus/content/groups/public</url>
        </pluginRepository>
      </pluginRepositories>
      <id>adobe-public</id>
    </profile>
  </profiles>
  <pluginGroups>
    <pluginGroup>org.apache.maven.plugins</pluginGroup>
    <pluginGroup>org.codehaus.mojo</pluginGroup>
  </pluginGroups>
</settings>

Initially, I thought I'd try ignoring these errors and carried on through the tutorial, but when I was editing the Hello World component I found my edits (in Eclipse) wouldn't show up CRXDE Lite or my local AEM instance of my 'Component Basics' page, so I back-tracked to where I started seeing errors and figured I'd better get everything setup good and proper.

Highlighted

dgordon86

Employee

06-05-2020

Hi @Blaiirrr !

It doesn't look like the adobe-public profile is active... you should see something like 

<activation>

        <activeByDefault>true</activeByDefault>

      </activation> 

or

<activeProfiles>

    <activeProfile>adobe-public</activeProfile>

  </activeProfiles>

 

Do you mind posting your full ~/.m2/settings.xml file?

Highlighted

Blaiirrr

06-05-2020

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.

Highlighted