Konrad Windszus

It is no longer deprecated since [AEMaaCS 17569](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/maintenance/latest). Compare https://javadoc.io/doc/com.adobe.aem/aem-sdk-api/2024.8.17465.20240813T175259Z-240700/org/apache/sling/settings/SlingSettingsService.html with https://javadoc.io/doc/com.adobe.aem/aem-sdk-api/latest/org/apache/sling/settings/SlingSettingsService.html.

Both cloud and classic version are having the same artifact id `acs-aem-commons-all` and therefore can be found in the same folder: https://repo1.maven.org/maven2/com/adobe/acs/acs-aem-commons-all/6.3.2/.

Feel free to come up with a PR for https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html

PRs are always appreciated in open source!

@davidjgonzalez Can you clarify if such a feature clashes with a product feature on Adobe's roadmap?

The COPYRIGHT file is IMHO more targeted at consumers, not at contributors. If you have to give Adobe the full copyright, this should be clearly mentioned in https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/CONTRIBUTING.md. In contrast...

Can some owners of this repo please clarify whether it is mandatory to grant the full copyright to Adobe for all new files? If that is the case then this...

@davidjgonzalez Can we please remove this enforced copyright donation. Recent changes made it clear that this whole project is not driven by Adobe as company but only engaged individuals. Forcing...

@henrykuijpers Which properties do you set on those nodes that get lost? The problem really is that the package needs to make sure that the ancestor nodes for its overlays...

Does any of your other packages contain `/apps/cq/core` as well? I am pretty sure this is a false positive as for overlays it is very common to enforce ancestor nodes...