AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Aem recompile jsp9/7/2023 To identify these deprecations, I used Eclipse compiler settings to generate errors for any usage of Deprecated API. However, it is always recommended to remove the deprecations in the code base. Having such a coding does not raise any issue as the product upgrade is backwards compatible. This step is required to fix the code which is deprecated after the upgrade. STEP 4: Check for deprecations in code base for both Java & JSP files This step ensures that the application runs and the functionalities work properly after successful build and deployment. So the bundle.jar can be used and referenced as an external jar dependency. If there is a need to validate whether it is the same bundle, then one can check the file present under same folder ( bundle-102 ). Now go to the crx-repository on the file system …./crx-quickstart->launchpad->felix->bundle- (bundle-102) Click on the dependency and make a note of the bundle id, i.e. Go to OSGI bundles ( ) and search for the dependency name (say Jackrabbit JCR Commons). So the trick is to retrieve it from AEM’s OSGI console. However, sometimes it would be required to get the version used in AEM installer (primarily because Adobe’s repository doesn’t get updated frequently). First of all, check for the latest version in Adobe’s Maven Repository and validate if the required version is present or not. We need the dependencies update in pom.xml to make the code compatible with the upgrade. STEP 2: Fix Incompatible Jars & Try to Compile Codebase For example, if we use MAVEN as a build tool then we can run the command ‘ mvn clean install -PautoInstallPackage ’ on the code base on the latest AEM version instance to deploy the code. If the build shows errors related to jars, which are incompatible then Step 2 would be required. The first step would be to build and deploy the existing code base for older AEM version to new AEM version. STEP 1: Deploy the existing code on new AEM instance The approach taken in a nutshell is ‘try to make the code compilable on the upgraded version, test the functionalities and then fix the deprecations.’ Here is a quick explanation of these steps, including the tips which worked for me in executing it. So through a couple of blogs, I want to focus on how to do the code base upgrade and what challenges are encountered during this process. ![]() The critical step was to make the code base ready to be deployed to an AEM 6.2 instance. Recently I was involved in planning and execution of an existing AEM 6.0 code base to AEM 6.2. Though Adobe documentation covers how to upgrade, but making the code compatible with the latest version is not discussed and is often ignored. Nonetheless, one of the last things anyone would like is to have an unsupported site which could run into any issue, plus to be always using a legacy version of AEM whereas the world is going gaga over new features provided by the latest version. The reason to upgrade a stable system and deal its complexities and issues involved with it can be quite debatable. Because of these complexities, the upgradations of AEM from one version to another one needs to be properly planned and executed. Adobe Experience Manager (AEM) is an Enterprise Web Content Management System which is used in high impact environments hosting voluminous pages and serving many users.It also involves integration with custom applications and customization of existing AEM features.
0 Comments
Read More
Leave a Reply. |