We have updated the service pack version from 6.5.10 to 6.5.15. I am just wondering, is it mandatory to update the uber-jar version to 6.5.15 as well? Our project's POM file is still pointing to uber jar version 6.5.10 and we haven't noticed any weird behavior as of now. What are the implications of not upgrading uber-jar to 6.5.15?
Thank you!
Solved! Go to Solution.
Views
Replies
Total Likes
Utilizing the version of Uber Jar in AEM, all features have been developed with backward compatibility in mind. You don't need to update the backend version of Uber Jar, but you should.. only because you will take advantage all the new features that comes with the service pack updates.
It is not, but good to have.
Uber jar is a single package, which will provide you almost all the api related to aem. So if you don't upgrade to latest and try to use some latest feature of AEM, specially introduced with latest service pack, you will will not be able to use that. There are other stuffs also, which stands helpfull so better to have updated one.
Hope this helps
Umesh Thakur
Utilizing the version of Uber Jar in AEM, all features have been developed with backward compatibility in mind. You don't need to update the backend version of Uber Jar, but you should.. only because you will take advantage all the new features that comes with the service pack updates.
@webdev91 When upgrading the service pack version of Adobe Experience Manager (AEM) from 6.5.10 to 6.5.15, it is generally recommended to also update the uber-jar version to 6.5.15.
If you do not update the uber-jar version to 6.5.15, you may encounter issues related to compatibility between the service pack and the uber-jar. For example, some new features or bug fixes in the service pack may require changes to the AEM runtime components, which are included in the uber-jar.
While you may not have noticed any issues with your project's POM file still pointing to the uber-jar version 6.5.10, it is possible that you may encounter issues in the future if there are any incompatibilities between the service pack and the older version of the uber-jar.
Therefore, it is generally recommended to update the uber-jar version to 6.5.15 when upgrading the service pack version of AEM. This can help ensure that your AEM instance is running with the latest runtime components and that any new features or bug fixes in the service pack are fully supported.
The uber-jar does not install in AEM, but it provides consolidated dependencies for development.
The only issue I can see if you don't update the uber jar version is that you will be compiling code with old version of libraries against the latest run time libraries.