I'm dealing with these errors in my bundle. I'm on aem 6.4I've done the following: Checked the IDE for any errors before the deployChanged the Core Bundle version Updated those dependencies with a newer version Right click on root POM -> Maven - > Generate Sources and Update FoldersWhat else can I do?

D

demd43642519

Solved

Bundle - Cannot be resolved dependecies

Forum|Forum|6 years ago
February 4, 2019
5 replies
3836 views

I'm dealing with these errors in my bundle.

I'm on aem 6.4

I've done the following:

Checked the IDE for any errors before the deploy
Changed the Core Bundle version
Updated those dependencies with a newer version
Right click on root POM -> Maven - > Generate Sources and Update Folders

What else can I do?

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 Gaurav-Behl

Your bundle requires "commons.net" version to be from 3.3-4 (exclusive) but AEM/Felix is unable to provide the same version. Hence, include "commons.net" bundle with either version from 3.3-4 and package it within your source code bundle. You may check if the same bundle is available in Felix with a different version or not?

Alternatively, if you don't need this bundle then add "!org.apache.commons.net.util" in the <Import-Package> of <maven-bundle-plugin>

Similar approach goes for "commons-validator". Provide either version from 1.6 to 2 or otherwise, block this dependency to be included in your import statements as applicable.

Maven Repository: commons-net » commons-net

Maven Repository: commons-validator » commons-validator

OR // based on your use case

<groupId>org.apache.felix</groupId>

<artifactId>maven-bundle-plugin</artifactId>

<extensions>true</extensions>

<configuration>

<instructions>

<Import-Package>!org.apache.comons.net.util,!org.apache.commons.validator.routines,*</Import-Package>

</instructions>

</configuration>

Gaurav-BehlAccepted solution