New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Raise warning to errors once decommissioning of deprecated packages is near #75

Open

kwin opened this issue Jun 1, 2021 · 1 comment

Contributor

kwin commented Jun 1, 2021

There is already a WARNING raised in case a deprecated API is used in the code via the analyser https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/src/main/java/org/apache/sling/feature/extension/apiregions/analyser/CheckDeprecatedApi.java. This is often not noticed by developers, so there should be configuration parameter to raise this warning to an error (failing the build) in case the decommissioning date according to https://experienceleague.adobe.com/docs/experience-manager-cloud-service/release-notes/deprecated-apis.html?lang=en comes closer.
This probably requires publishing that information in a machine-readable way. The configuration parameter should allow to define a time span from which on the WARN is raised to an ERROR automatically (by default 4 weeks prior to removal).

Contributor Author

kwin commented Jun 8, 2021

https://issues.apache.org/jira/browse/SLING-10471

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment