Add analyser for OSGi config org.apache.sling.commons.log.LogManager.factory.config to always have file error.log · Issue #318 · adobe/aemanalyser-maven-plugin · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
kwin
changed the title
Add analyser for org.apache.sling.commons.log.LogManager.factory.config to always have file error.log
Add analyser for OSGi config org.apache.sling.commons.log.LogManager.factory.config to always have file error.log
Apr 11, 2025
Uh oh!
There was an error while loading. Please reload this page.
As other file names are not considered one should always point all custom loggers to
logs/error.log
(https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/logs#custom-log-files). Although the check configuration analyser in https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/src/main/java/org/apache/sling/feature/extension/apiregions/analyser/CheckConfigurationApi.java is suitable for this kind of check the property restriction (https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md#properties) is currently not outlined in thefactory-configurations
section of https://repo1.maven.org/maven2/com/adobe/aem/aem-sdk-api/2025.3.20133.20250325T063357Z-250300/aem-sdk-api-2025.3.20133.20250325T063357Z-250300-aem-publish-sdk.slingosgifeatureThe text was updated successfully, but these errors were encountered: