Examples:
Thank you!
Solved! Go to Solution.
Views
Replies
Total Likes
The release note for each service pack explicitly calls out the uber-jar details. For example the uber jar details for the latest service pack (6.5.17 as of today) are available here
For previous versions look for specific service pack page. For instance 6.5.16 look here.
Last but not the least, never assume that the service pack and uber jar version will be same. As sometime the uber-jar may not require changes and in such cases, the previous version is used. That also gets called out explicitly in the documentation. See the 6.5.16 link above for example.
HTH.
Hello @jayv25585659
It is always recommended to update uber jar dependency, whenver you upgrade AEM.
This helps ensure that your application's runtime environment matches the updated version and its dependencies. This is especially important if there were improvements, changes, bug fixes or security updates related to the dependencies between version 6.5.0 and 6.5.17.
For any deprecated dependencies, please refer to javadocs https://javadoc.io/doc/com.adobe.aem/uber-jar/latest/deprecated-list.html .
Please check if "javac-Xlint:deprecation" would also help find deprecations easily. https://docs.oracle.com/en/java/javase/17/core/enhanced-deprecation1.html#GUID-97A6BB09-6F7D-4ED0-BF...
AEM release notes would convey about major updates in release. It would not contain intricate details about uber jar.
The release note for each service pack explicitly calls out the uber-jar details. For example the uber jar details for the latest service pack (6.5.17 as of today) are available here
For previous versions look for specific service pack page. For instance 6.5.16 look here.
Last but not the least, never assume that the service pack and uber jar version will be same. As sometime the uber-jar may not require changes and in such cases, the previous version is used. That also gets called out explicitly in the documentation. See the 6.5.16 link above for example.
HTH.