It would be a product bug. I have not come across this.As a workaround, You can overlay instead of proxying the component and change the imageDelegate to image(v3) in the teaser. 

You would need to add child nodes inside the style node in order for them to appear in the RT Editor.You would need to declare a value and then a CSS name on which styling can be applied Something like this:<styles jcr:primaryType="nt:unstructured" features="*"> <styles jcr:primaryType="nt:unst...

You may need to add params with your image src if that's the case. Are you using JPG or PNG.Go through this documentation, it should help in increasing sharpness & size.https://experienceleague.adobe.com/docs/experience-manager-64/assets/dynamic/best-practices-for-optimizing-the-quality-of-your-imag...

This is not possible with Sightly.This is from official documentation:Separation of Concerns: The expressiveness of the Sightly template language is purposely limited, in order to make sure that a real programming language is used to express the corresponding presentation logic. This optional logic ...

Same thing for v1 as well. It uses Image(v2) instead of v3. 

Hi @maheshp , If you're using teaser(v2) proxy. It uses an imageDelegate to image(v3). You can adjust quality of the image in the design dialog for teaser. 

AEM as a Cloud Service only supports Java 11+.And if you try to deploy code with, say Java 8, it won't work. It will throw error an bundles will not get resolved.

Please share stderr logs and error logs.

Did you add adobe public profile in your setting.xml in maven?Create a file named settings.xml at ~/.m2/settings.xml if it doesn’t exist already.Add the adobe-public profile to the settings.xml file<settings xmlns="https://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="https://www.w3.org/2001/XMLSche...

Hi @prash0905 ,Can you share the .xml for the dialog/field which you have created.