Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

ACS commons maven build error on AEM as a cloud service

Avatar

Community Advisor

Hi All,

We are trying to include acs-commons latest version 6.0.14 but we are getting errors while building the package ( AEM cloud service)

 

Error:

SNAPSHOT: com.adobe.acs:acs-aem-commons-content:zip:min:6.0.14 was not found in https://repo.adobe.com/nexus/content/groups/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of adobe-public-releases has elapsed or updates are forced.

 

Does anyone faced the same or any suggestions to resolve this issue.

 

Thanks

Himanshu

Himanshu Jain
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

So that's the Root Cause. 6.0.14 is not present in either maven public repo or nexus-repo.

Just checked they change their package name from 6.x.x. That's why the old dependency format is not working. Also, I am not sure about the new dependency.

https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases 

Sady_Rifat_0-1689751279829.png

If you found the new dependency please let me know also. Otherwise 2 things you can do,

  • Download the zip package(6.0.14) from github and install via package manager. On this case, you need to remove the dependency
  • If your company has own nexus repo then you can deploy the latest version on their and able to resolve it.

View solution in original post

10 Replies

Avatar

Employee Advisor

Hi,

 

To resolve the issue, ensure that the repository configuration is correct, check if the desired version is available, force an update by deleting the local cache, or explore alternative repositories.

Avatar

Community Advisor

Hello @Himanshu_Jain ,

Last week I faced the same Nexus Repository error "This failure was cached in the local repository...." for one of my internal project.

My finding was:

  • Double check your .m2/setting.xml file and check the repositories are correct
  • Delete the internal cache repository. .m2/com/adobe/acs
  • Invalid cache for your IDE

Note that in maven public repository ACS Commons version is available up to 5.7.0 https://mvnrepository.com/artifact/com.adobe.acs/acs-aem-commons-content 

Hope in the Nexus repository your desired version is available. Please recheck this.

Avatar

Community Advisor

Issue is with the latest one 6.0.14

Himanshu Jain

Avatar

Community Advisor

@Himanshu_Jain , Sorry for the confusion, My point was in Maven public repository 6.0.14 was not present. That's why it's trying to fetch the acs-aem-commons from nexus repository. 

I think you crossed checked that the 6.0.14 version is present in Nexus repository?

Avatar

Correct answer by
Community Advisor

So that's the Root Cause. 6.0.14 is not present in either maven public repo or nexus-repo.

Just checked they change their package name from 6.x.x. That's why the old dependency format is not working. Also, I am not sure about the new dependency.

https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases 

Sady_Rifat_0-1689751279829.png

If you found the new dependency please let me know also. Otherwise 2 things you can do,

  • Download the zip package(6.0.14) from github and install via package manager. On this case, you need to remove the dependency
  • If your company has own nexus repo then you can deploy the latest version on their and able to resolve it.

Avatar

Community Advisor

@Sady_Rifat  We cannot install in cloud service it needs to be pushed via pipeline only .

Himanshu Jain

Avatar

Employee

I can see the package is present in Nexus repo.

https://repo.maven.apache.org/maven2

 

NishantSingh_0-1689769843846.png

it seems you are using classifier as min. can you please remove 

 <classifier>min</classifier>

 from POM and check.

Avatar

Community Advisor

@Nishant-Singh Thanks for highlighting , it was not available till day before yesterday .

 

Thanks

Himanshu

Himanshu Jain