@Amit-Tiwari  Have you tried both of these options? https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/create-application-project/build-environment-details.html?lang=en#alternate-maven-jdk-versionIf still does not work, please raise Ado...

By default 10 results are shown but you can increase the limit using p.limit=N or p.limit=-1(for all results) where N stands for number of result you want to see.

@MarkECis References of assets wont be updated in page automatically. You have to write script to update content wherever old asset path is referred. You have to be cautious as asset path might be available in Richtext as well, handling update of it would be tricky. Also you have to update collectio...

Adding dependency in pom.xml wont upload the bundle in AEM until you specifically embed it. Gson comes with Uber jar as well and probably the version of same would be reflecting in your bundle. Please elaborate more to understand what you are trying to achieve. 

I see you are using onedrive directory. Sometime onedrive takes time to sync files and it causes issue. Can you please try outside onedrive folder like C or D Drive and see if same behavior is observed? 

Is there any dispatcher in front of AEM when you are trying to hit? It does not seem to be usual that you are getting bad request and AEM is actually receiving the request. Did you see anything in request.log?

You can use rendercondition as explained by @aanchal-sikkaIf possible please avoid doing such customization as you may face issue with upgrades.

As explained by @BrianKasingli, it is good to implement redirects on Dispatcher or CDN. Otherwise you can use OOTB feature to do redirect i.e. Redirect property present in page properties.  https://medium.com/tech-learnings/adobe-experience-manager-aem-implementing-custom-redirect-vanity-urls-manag...

@RooRue If Asset is still linking to its old version, can you please try purging older versions and see if it helps. https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/monitoring-and-maintaining.html?lang=en  

@skumari Please update if your local issue got resolved and what was the fix. It will help others as well.