Maven Build Dependency Error | Community
Skip to main content
NageshRaja
New Participant
July 31, 2025
Solved

Maven Build Dependency Error

  • July 31, 2025
  • 3 replies
  • 596 views

Hey guys,

 

I am trying to add a new dependency with the objective to create CFs programatically.

I added the below dependency in my core pom.xml

<dependency>
<groupId>com.adobe.cq.dam</groupId>
<artifactId>cq-dam-cfm-api</artifactId>
<version>1.10.0</version> <!--${aem.sdk.api}-->
<scope>provided</scope>
</dependency>

But my build log is giving the below error - 

 

[ERROR] Failed to execute goal on project ctcweb.core.bundle: Could not resolve dependencies for project com.abc.aem:abc.core.bundle:jar:1.0.0-SNAPSHOT
[ERROR] dependency: com.adobe.cq.dam:cq-dam-cfm-api:jar:1.10.0 (provided)
[ERROR]         Could not find artifact com.adobe.cq.dam:cq-dam-cfm-api:jar:1.10.0 in adobe-public-mirror (https://repo.adobe.com/nexus/content/groups/public/)

 

Any suggestions would be appreciated!

 

Thanks,

Nagesh

3 replies

kautuk_sahni
Employee
August 4, 2025

@nageshraja Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni
arunpatidar
arunpatidarAccepted solution
New Participant
August 1, 2025
New Participant
July 31, 2025

Hi @nageshraja ,

 

1. Check Adobe Repo Access
Ensure this repo is in your settings.xml:
https://repo.adobe.com/nexus/content/groups/public/

 

2. Verify Artifact Availability
Version 1.10.0 may not exist publicly. Try:-

  • Diffrent available versions
  • Searching in your local AEM SDK libs

3. Install JAR Manually (if local):


mvn install:install-file \
-Dfile=/path/to/cq-dam-cfm-api-1.10.0.jar \
-DgroupId=com.adobe.cq.dam \
-DartifactId=cq-dam-cfm-api \
-Dversion=1.10.0 \
-Dpackaging=jar

 

4. Use AEM SDK BOM (If you're using AEM as a Cloud Service)
Manage versions via Adobe’s BOM instead of hardcoding.