Hey Created a support case with Adobe customer care, and they pointed out that the way you're referencing the uber jar has changed. As outlined on the SP6 release notes, the new way to include the uber-jar is: com.adobe.aem uber-jar 6.5.6-1.0 Hope this helps! With kind regards Koen

Re: Configuring Style System for Nested Components - Adobe Experience Manager

From what I've noticed, it looks like the wrapper div is not being generated when including a component. Because of this, the style system cannot add any classes to it. Adding @decoration=true to the data-sly-resource will include the wrapper div (which is important, because otherwise your cq:htmlTag might not be taken into account).

(val/1000)?string[".0"]}K

Re: Configuring Style System for Nested Components - Adobe Experience Manager

(val/1000)?string[".0"]}K

Re: Recompile JSPs not available in AEM 6.5 - Adobe Experience Manager

Thanks!

(val/1000)?string[".0"]}K

Recompile JSPs not available in AEM 6.5 - Adobe Experience Manager

Some UI issues need a recompilation of the JSPs in order to be resolved (/system/console/slingjsp). However, in AEM 6.5 (tested on an OOTB installation with no additional packages installed) the console with which this is usually done is no longer available. It is not present in the menu, nor is the URL accessible directly.AEM 6.3:AEM 6.5:Is there an other way to recompile the JSPs?Thanks in advance for your feedback!

(val/1000)?string[".0"]}K

Re: AEM 6.4 /api/screens-dcc/devices/stati WARNING - Adobe Experience Manager

Can confirm this is still an issue in AEM 6.4.3 (still have to check with 6.4.4). Thanks for the workaround though, we'll implement that in the meantime

(val/1000)?string[".0"]}K