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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Application Insights dependency issue in AEM

Avatar

Level 1

I have included the maven dependency for application insights as below

 

<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>applicationinsights-web-auto</artifactId>
<version>2.5.0</version>
<scope>provided</scope>
</dependency>

 

After that also Im facing the following error in OSGI bundle

com.microsoft.applicationinsights -- Cannot be resolved
com.microsoft.applicationinsights.channel -- Cannot be resolved
com.microsoft.applicationinsights.extensibility -- Cannot be resolved
com.microsoft.applicationinsights.extensibility.context -- Cannot be resolved
com.microsoft.applicationinsights.internal.util -- Cannot be resolved
com.microsoft.applicationinsights.telemetry -- Cannot be resolved

Java 11

AEM 6.5
Can anyone pls tell me how to resolve the issue..

TIA

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

It's not sufficient to just add the maven dependencies to the build classpath, because these dependencies are not present by default in the runtime (in AEM itself). So you either add these dependencies as OSGI dependencies to your content package, or you embed these dependencies into your application bundle.

View solution in original post

0 Replies

Avatar

Community Advisor

@Archana_VA_007 

Remove <scope>provided</scope> and check once, which means the container (here OSGi) is providing the implementation for that. 

Check the scope instructions: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Sc...

 

Avatar

Correct answer by
Employee Advisor

It's not sufficient to just add the maven dependencies to the build classpath, because these dependencies are not present by default in the runtime (in AEM itself). So you either add these dependencies as OSGI dependencies to your content package, or you embed these dependencies into your application bundle.