Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

com.akamai.edgegrid.signer.exceptions,version=[4.0,5) -- Cannot be resolved

Avatar

Level 3

Hi,

Iam getting below error when try to activate bundles.

 

com.akamai.edgegrid.signer.exceptions,version=[4.0,5) -- Cannot be resolved

 

I am added only 4.0.0 version of  “edgegrid-signer-core” dependency. And in contains exceptions class. But  version 4.0.5 version I can see in bundles.

 

if iam adding lover version my code implementation getting dependency error.

 

Can any one suggest how to fix this issue?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @mohanasundaramp,

 

Can you please check which version of  “edgegrid-signer-core” dependency is installed in your environment. The dependency error says it is not able to find the bundle [version or bundle itself] mentioned in the pom.xml.

 

Check my answer here to know the different ways of installing a bundle.

 

Hope this helps.

 

Thanks,

Kiran Vedantam.

View solution in original post

7 Replies

Avatar

Correct answer by
Community Advisor

Hi @mohanasundaramp,

 

Can you please check which version of  “edgegrid-signer-core” dependency is installed in your environment. The dependency error says it is not able to find the bundle [version or bundle itself] mentioned in the pom.xml.

 

Check my answer here to know the different ways of installing a bundle.

 

Hope this helps.

 

Thanks,

Kiran Vedantam.

Avatar

Community Advisor

@mohanasundaramp Did you install the already available bundle or any custom bundle ? Becoz as the error says

 

com.akamai.edgegrid.signer.exceptions,version=[4.0,5) -- Cannot be resolved

 

Your  “edgegrid-signer-core”  has a dependency to the above bundle and the version is not available in your felix console. You can either check the bundle which has above dependency with version, or if you are using custom bundle , please remove the version references in the META-INF and rebuild the bundle. ( do this only if it is custom bundle)

 

Update :- I was searching pom for the above classes and got this one. I am not sure if it has the above class, but can you try https://mvnrepository.com/artifact/com.akamai.edgegrid/edgegrid-signer-core/4.0.1

 

Thanks

Veena

Avatar

Level 3

iam using dependency in pom file

<dependency>
<groupId>com.akamai.edgegrid</groupId>
<artifactId>edgegrid-signer-apache-http-client</artifactId>
<version>4.0.0</version>
</dependency>

 

<dependency>
<groupId>com.akamai.edgegrid</groupId>
<artifactId>edgegrid-signer-apache-http-client</artifactId>
<version>4.0.0</version>
<scope>provided</scope>
</dependency>

 

 

And not able to delete in  META-INF.

Avatar

Community Advisor
I was searching pom for the above classes and got this one. I am not sure if it has the above class, but can you try https://mvnrepository.com/artifact/com.akamai.edgegrid/edgegrid-signer-core/4.0.1

Avatar

Level 3
Thanks for your post. 4.0.1 core also i have validated. still facing same issue.

Avatar

Employee
Adding a depdency in your pom is NOT the same as embedding the dependency and deploying it as part of your package to AEM. You need to do the latter. You can do this in a similar fashion as you embed your Core OSGi bundle in your ui.apps content package.

Avatar

Level 3

Thanks all for your comments.

Finally it's working after adding the jar bundles in OSGI bundles section.