Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
AEM Service pack 6.5.19 upgrade issues
You need to update the Uber jar dependency as <dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.19</version>
<scope>provided</scope>
</dependency>
now there is no classifier as explained on https://experienceleague.adobe.com/docs/experience-manager-65/content/release-notes/release-notes.ht...
I haven’t upgraded to sp 19 but it seems mockito-core 3.4.6 version is very old. May be try to update the version of mockito and junit-bom to latest one. May I now the prior version from which you are upgrading to 6.5.19?
@DPrakashRaj I did the below
1. Removed the classifier from uber jar update.
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.19</version>
<scope>provided</scope>
</dependency>
2. Updated mockito-core and junit-bom to latest as below
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>5.8.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-junit-jupiter</artifactId>
<version>5.8.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-inline</artifactId>
<version>5.8.0</version>
<scope>test</scope>
</dependency>
and
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>5.10.1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Earlier org.junit.junit-bom was 5.4.1 and mockito was 3.4.6
But after this changes, I get the below error. Its seems not able to download the dependency
The above error shows that mockito-inline:5.8.0 is not present in the repository. Check on https://repo.maven.apache.org/maven2. It seems latest version there is 5.2.0. Try with that one.you can’t browse repo.abobe.com so try with some lower version to check if it downloads. Hope that helps
Thanks @DPrakashRaj . Did this change as well. Now it's a different error, I am looking into after the change you mentioned.
If, I comment the full class, it throws another mockito error with a different error in another class.
Seems like some classes have changed with dependencies on uber jar update.
Curious to see, if anyone has done SP19 upgrade successfully.
Ok it seems mockito 5.0.0 and above are not compatible with jdk 8. If you are using jdk can you try mockito4.9.0 and see if it gets resolved?
@DPrakashRaj Yes. Like I commented above using 4.9.0 now since I found mockito 5 and above doesn't work for java8, but still lot of errors as below and working through it
I am able to build and deploy AEM maven project with aem-uber jar 6.5.19 without any issue after upgradimg AEM to 6.5.19 with java 8
1) uber jar depenedency
<!-- Adobe AEM Dependencies -->
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.19</version>
<scope>provided</scope>
</dependency>
2) mockito and junit
<!-- Testing -->
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>5.8.2</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>4.1.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-junit-jupiter</artifactId>
<version>4.1.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit-addons</groupId>
<artifactId>junit-addons</artifactId>
<version>1.4</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>io.wcm</groupId>
<artifactId>io.wcm.testing.aem-mock.junit5</artifactId>
<version>4.1.8</version>
<scope>test</scope>
</dependency>
can you check the class for context object
Asset asset1 = context.create().asset("/content/dam/asset.jpg", new InputStream() {
@DPrakashRaj That is good that worked for you. But can you confirm if you have aem context used in any of your junit classes to set objects?
I tried with the same versions as you pinged above, but the failure is the same as below. I think the below class is deprecated.
Please find my test class below.
This is the reason I created an internal class for field setter , as I posted above, but that too didn't help, though I removed that now for testing the version changes alone as per your last post.
But we tried commenting these classes to make sure uber jar update to the instance will fix the SSO issue and other outstanding issues we have with respect to SP19 upgrade. So that test was done, but all issues still persist. we have opened separate adobe support ticket for each issue, but they are all slowly progressing.
private final AemContext context = AppAemContext.newAemContext();
private TestClass hello;
private Page page;
private Resource resource;
@BeforeEach
public void setup() throws Exception {
// prepare a page with a test resource
page = context.create().page("/content/mypage");
resource = context.create().resource(page, "hello",
"sling:resourceType", "site/components/test");
// create sling model
hello = resource.adaptTo(TestClass.class);
}
@test
void testGetMessage() throws Exception {
// some very basic junit tests
String msg = hello.getMessage();
assertNotNull(msg);
assertTrue(StringUtils.contains(msg, resource.getResourceType()));
assertTrue(StringUtils.contains(msg, page.getPath()));
}
Recommendation is to update the uber jar corresponding to the AEM version + SP.
This assure we are using the latest features and fixes
You might want to consider updating versions of all dependencies. All of them seem to be pretty old versions.
Aanchal Sikka
@P_V_Nair Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Kautuk Sahni
Related Conversations
