7/5/2023 0 Comments Aem recompile jsp![]() ![]() It is always a best practice to include the Uber Jar as a single dependency instead of including individual AEM API dependencies. The AEM Uber jar includes all AEM APIs as a single dependency in your Maven project’s pom.xml. Iterative testing of the code base against the target version of AEM and subsequent bug fixes is managed in this branch. A dedicated branch in version control should be created for managing any changes needed for the code base in the target version of AEM. Upgrade the Code Base Create a Dedicated Branch for 6.5 Code in Version ControlĪll code and configurations required for your AEM implementation should be managed using some form of version control. See the Backward Compatibility in AEM 6.5 page for more details. It can also help you decide whether you want to run in compatibility mode or update your customizations to use all the new AEM 6.5 features. In addition to optionally upgrading your code base and customizations to work with the new AEM version, 6.5 also helps manage your customizations more efficiently with the Backward Compatibility feature as described on this page.Īs mentioned above and shown in the diagram below, running the Pattern Detector in the first step can help you assess the overall complexity of the upgrade. ![]() For example, it might include refactoring the code to avoid traversing the repository, custom indexing to optimize search, or use of unordered nodes in JCR, among others. Based on observations made in testing, there could be ways to optimize the custom code. Repeat Dev-Cycle as necessary until all bugs are fixed.īefore proceeding with an upgrade, you should have a stable application code base that has been thoroughly tested against the target version of AEM. Any bugs found should be fixed and committed to the 6.5 code base. QA Validation and Bug fix - QA should validate the application on both Author and Publish instances of 6.5. Updated code base and a representative sample of content (from current production) should be deployed. Includes UI Search Forms, Assets Customizations, anything using /mnt/overlayĭeploy to 6.5 Environment - A clean instance of AEM 6.5 (Author + Publish) should be stood up in a Dev/QA environment. Update AEM Customizations* - *Any customizations or extensions to AEM should be updated/validated to work in 6.5 and added to the 6.5 code base. **Compile with 6.5 Uber jar **- Update code base POMs to point to 6.5 uber jar and compile code against it. Use info from Pre-Upgrade Compatibility to plan areas of code to update. **Develop Code Base for 6.5 **- Create a dedicated branch or repository for the code base for the Target version. ![]() See Backward Compatibility in AEM 6.5 for more details. Or, you can decide to do development after upgrade, and move to step 2. If there are incompatibilities reported, you can choose run in compatibility mode and defer your development for new 6.5 features or compatibility. You can still choose to do new development for using 6.5 functionality, but you do not need it just for maintaining compatibility. If none exists, then your deployment is already 6.5 compatible. The Pattern Detection report gives you an indication of any incompatibilities in your code. You get a pattern detector report that contains more details on areas that must be addressed in addition to the unavailable APIs/bundles in the Target version of AEM. Pattern Detector - Run the Pattern Detector as described in upgrade planning and described in detail in this page. ![]() When planning an upgrade, the following areas of an implementation must be investigated and addressed. ![]()
0 Comments
Leave a Reply. |