david g.
Fine with me as well. There have been many years for users to switch to later versions of Java. This would bump us to 7.0.0
Similar approach was taken in the ASC's RequireAEMImpl [1] - basically, we create an OSGI configuration and put it in /apps/asset-share-commons/config.publish with the service.type value of "publish" ... and the...
@royteeuwen, unfortunately, nothing in the product itself - The POV being that things that depend on author/publish should depend on an OSGi configuration value that is set VIA the author/publish...
To be clear, I'm not disagreeing :) We can incorporate this into RequireAEM if we want (it's implemented in ASC now, so we can copy it over). https://github.com/adobe/asset-share-commons/blob/develop/core/src/main/java/com/adobe/aem/commons/assetshare/util/impl/RequireAemImpl.java#L82
💯 agree
Changed "Chat"-> "Discuss" and linked to GH Discussions on website
Fixed in 6.2.0.
I dont know what these libraries do and why they would break unrelated behavior. Can you provide more color on what these are? Im not sure why they would be...
Ah! Sounds like these libraries are breaking something in the JSON export contract in AEM. I suggest logging an issue on those projects as MCP works w vanilla AEM.
@AsadShafi-AnF can you provide the ERRRO form the log file when this happens?