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
cannot find uber jar 16 in public repo?
1 Accepted Solution
Correct answer by
I GUESS there are not any "backend" changes that required a new jar to be generated. As you know the SP does include more than AEM core fixes, sometimes UI, integrations, etc. I mean, this is not the first time these things happen, I have seen this pattern a couple of times so far
Esteban Bustamante
The uber jar is not necessarily updated on each Service Pack release, in some increments you need to use the previous uber.jar, that is exactly the case for SP16 and the reason why there is not a uber 16 jar.
You can check the releases notes here: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/6.5.16.html...
Additionally, you can find the list of available Uber jar here: https://repo.maven.apache.org/maven2/com/adobe/aem/uber-jar/
Esteban Bustamante
Correct answer by
I GUESS there are not any "backend" changes that required a new jar to be generated. As you know the SP does include more than AEM core fixes, sometimes UI, integrations, etc. I mean, this is not the first time these things happen, I have seen this pattern a couple of times so far
Esteban Bustamante
Related Conversations
