You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/10/03 18:48:43 UTC
[jira] [Commented] (KARAF-2498) Change log level to DEBUG for
Cellar blacklist/whitelist message
[ https://issues.apache.org/jira/browse/KARAF-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785334#comment-13785334 ]
Jean-Baptiste Onofré commented on KARAF-2498:
---------------------------------------------
Fixed on cellar-2.3.x: http://svn.apache.org/viewvc?view=revision&revision=1528931
> Change log level to DEBUG for Cellar blacklist/whitelist message
> ----------------------------------------------------------------
>
> Key: KARAF-2498
> URL: https://issues.apache.org/jira/browse/KARAF-2498
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-bundle, cellar-config, cellar-core, cellar-dosgi, cellar-features
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.3.2
>
>
> When installing Cellar or sending cluster events, Cellar is very verbose when it checks the blacklists/whitelists.
> We have a lot of messages like this:
> CELLAR FEATURES: feature cellar is marked BLOCKED OUTBOUND for cluster group default
> This kind of messages are not really helpful for end users, it's mostly useful to identify some behaviours.
> So, these messages are not really WARN message, they should be DEBUG message.
--
This message was sent by Atlassian JIRA
(v6.1#6144)