com.day.cq.dam.api.s7dam.scene7 does not exist after uber-jar-6.5.7 upgrade

Avatar

Avatar
Validate 1
Level 2
samsundar23
Level 2

Likes

4 likes

Total Posts

62 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
samsundar23
Level 2

Likes

4 likes

Total Posts

62 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile
samsundar23
Level 2

03-03-2021

I'm upgrading SP7 to my AEM 6.5.

After updating uber-jar-6.5.7 in my pom.xml. I get the below error.

Kindly help.

 

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 39.045 s
[INFO] Finished at: 2021-03-04T12:43:10+05:30
[INFO] Final Memory: 34M/397M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project temp.core: Compilation failure: Compilation failure:
[ERROR] /C:/CBA/my_LEGO/aem.temp-lego/bundles/core/src/main/java/com/temp/services/impl/DynamicMediaProcessorImpl.java:[7,39] package com.day.cq.dam.api.s7dam.scene7 does not exist
[ERROR] /C:/CBA/my_LEGO/aem.temp-lego/bundles/core/src/main/java/com/temp/services/impl/DynamicMediaProcessorImpl.java:[38,13] cannot find symbol
[ERROR] symbol: class ImageUrlApi
[ERROR] location: class com.temp.services.impl.DynamicMediaProcessorImpl
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
Employee
VikramGaur
Employee

Likes

42 likes

Total Posts

68 posts

Correct reply

24 solutions
Top badges earned
Establish
Give Back 5
Give Back 3
Give Back
Boost 5
View profile

Avatar
Establish
Employee
VikramGaur
Employee

Likes

42 likes

Total Posts

68 posts

Correct reply

24 solutions
Top badges earned
Establish
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
VikramGaur
Employee

05-03-2021

Hi,
Welcome to AEM Community.

I hope you have download the latest uber.jar from Maven central after upgrading to AEM 6.5.7

You may try adding this dependency

<------

<dependency>

      <groupId>com.adobe.aem</groupId>

      <artifactId>uber-jar</artifactId>

      <version>6.5.7</version>

       <scope>provided</scope>

</dependency>

------>

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 2
samsundar23
Level 2

Likes

4 likes

Total Posts

62 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
samsundar23
Level 2

Likes

4 likes

Total Posts

62 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile
samsundar23
Level 2

07-03-2021

Hello, 

My uber-jar changes are already part of my pom.xml

My primary problem has been after the upgrade to uber-jar-6.5.7.

Avatar

Avatar
Ignite 1
MVP
SureshDhulipudi
MVP

Likes

163 likes

Total Posts

174 posts

Correct reply

49 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
MVP
SureshDhulipudi
MVP

Likes

163 likes

Total Posts

174 posts

Correct reply

49 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
SureshDhulipudi
MVP

04-03-2021

check this class - DynamicMediaProcessorImpl and resolve the package com.day.cq.dam.api.s7dam.scene7

If you are using any IDE, it will give you option to import/resolve/fix project set up

or you can try, just mvn clean install to import all dependencies