Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

aem-sample-we-retail-master Issues

manikanthar1295
Level 4
Level 4

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

 

manikanthar1295_0-1620649673305.png

 

 

1 Accepted Solution
KiranVedantam1992
Correct answer by
Community Advisor
Community Advisor

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?

 

KiranVedantam1992_0-1620650177330.png

Hope this helps.

 

Thanks,

Kiran Vedantam

 

View solution in original post

2 Replies
KiranVedantam1992
Correct answer by
Community Advisor
Community Advisor

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?

 

KiranVedantam1992_0-1620650177330.png

Hope this helps.

 

Thanks,

Kiran Vedantam

 

View solution in original post

markus_bulla_adobe
Employee
Employee

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!