[
https://issues.apache.org/jira/browse/SLING-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157915#comment-17157915
]
Ashish Chopra commented on SLING-8940:
--------------------------------------
hi [~rombert], [~bosschaert], could you also consider including the ability to
control analyser severity through plugin's user-properties in this issue? This
will help in cases where we'd like to reduce the analyser-severity for sub-jobs
in the CI. Please see [0]
[0]
https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/pull/7#issuecomment-658566041
> Configurable severity for analyser messages
> -------------------------------------------
>
> Key: SLING-8940
> URL: https://issues.apache.org/jira/browse/SLING-8940
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Feature Model Analyser 1.3.2
>
>
> In the context SLING-8938 we also discussed the option of making message
> severity configurable.
> The proposal from the mailing list was to create a code for each class of
> reported issues, and then create mappings of the form
> {{analyser_code.message_code}}, e.g.
> {noformat}metatype-consistency.property-not-in-metatype=WARN{noformat}
> A further improvement (maybe as a separate issue) would be to also be able to
> also filter further on the message or other structured properties. The use
> case would be to lower the severity of unactionable items from bundles that
> are not under control of the developer, e.g.
> {noformat}[WARNING] Bundle logback-core:1.2.3 is importing package(s)
> [org.codehaus.commons.compiler, org.codehaus.janino] without specifying a
> version range{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
