aem-sample-we-retail-master Issues | Community
Skip to main content
manikanthar1295
manikanthar1295
Level 5
May 10, 2021
Solved

aem-sample-we-retail-master Issues

  • May 10, 2021
  • 2 replies
  • 1130 views

Hi,

i have downloaded aem-sample-we-retail-master code git and i have build in my local by using mvn -PautoInstallPackage clean install command while building i got below error.

Any help to solve this build issue kindly suggest

 

 

 

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

Hi, @manikanthar1295.

 

As per the screenshot, the user that you are using to install the code into your repository does not have access. hence you see "Unauthorized."

 

Can you please check the user in your main pom.xml and correct the id and pwd like below?

 

Hope this helps.

 

Thanks,

Kiran Vedantam

 

2 replies

Kiran_Vedantam
Community Advisor
Kiran_VedantamCommunity AdvisorAccepted solution
Community Advisor
May 10, 2021

Hi, @manikanthar1295.

 

As per the screenshot, the user that you are using to install the code into your repository does not have access. hence you see "Unauthorized."

 

Can you please check the user in your main pom.xml and correct the id and pwd like below?

 

Hope this helps.

 

Thanks,

Kiran Vedantam

 

    MarkusBullaAdobe
    Adobe Employee
    MarkusBullaAdobeAdobe Employee
    Adobe Employee
    May 10, 2021

    Hi @manikanthar1295!

     

    The error message of your Maven build points out that the request to AEMs Package Manager to install the application package to your AEM instance is unauthorized. Please double check that the according credentials are present and correct in your projects pom.xml file (in the projects "properties" section):

    • sling.user
    • sling.password

    You will find an example in the pom.xml from the example project.

    If you don't want to put your credentials into the pom.xml file you can also provide them as parameters to the Maven build on the command line or source them from a different source, e. g. from an environment variable.

     

    Hope that helps!

      Terms & ConditionsAccessibility statement

      Loading footer...