sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A. J. David Bosschaert (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SLING-8940) Configurable severity for analyser messages
Date Thu, 27 Feb 2020 13:33:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

A. J. David Bosschaert updated SLING-8940:
------------------------------------------
    Fix Version/s:     (was: Feature Model Analyser 1.2.6)
                   Feature Model Analyser 1.2.8

> 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.2.8
>
>
> 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)

Mime
View raw message