(james-jdkim) 02/03: Update commons-logging

2024-07-26 Thread btellier
Update commons-logging --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index e04cb57..d5e6970 100644 --- a/pom.xml +++ b/pom.xml @@ -63,7 +63,7 @@ 0.8.11 1.15 -1.2 +1.3.3 3.6.0 1.8

[jira] [Updated] (JDKIM-47) James-jdkim should not depend on a logging library implementation

2021-12-16 Thread Tran Hong Quan (Jira)
-jdkim using log4j as a logging library implementation. James-jdkim himself is a library so it should not depend on any logging implementation and should use slf4j abstraction instead. We can use slf4j in src/main and keep log4j in src/test was: Right now, James-jdkim using log4j as a logging

[jira] [Created] (JDKIM-47) James-jdkim should not depend on a logging library implementation

2021-12-16 Thread Tran Hong Quan (Jira)
Tran Hong Quan created JDKIM-47: --- Summary: James-jdkim should not depend on a logging library implementation Key: JDKIM-47 URL: https://issues.apache.org/jira/browse/JDKIM-47 Project: James jDKIM

[jira] [Closed] (IMAP-88) Add User Name to context sensitive logging messages

2021-09-05 Thread Benoit Tellier (Jira)
ext sensitive logging messages > --- > > Key: IMAP-88 > URL: https://issues.apache.org/jira/browse/IMAP-88 > Project: James Imap > Issue Type: Improvement > Com

[jira] [Closed] (JAMES-3420) WebAdmin request logging should not log password

2020-10-09 Thread Benoit Tellier (Jira)
/3876 contributed this > WebAdmin request logging should not log password > > > Key: JAMES-3420 > URL: https://issues.apache.org/jira/browse/JAMES-3420 > Project: James Server >

[jira] [Commented] (JAMES-3420) WebAdmin request logging should not log password

2020-10-08 Thread Benoit Tellier (Jira)
ebAdmin request logging should not log password > > > Key: JAMES-3420 > URL: https://issues.apache.org/jira/browse/JAMES-3420 > Project: James Server > Issue Type: Bug >

[jira] [Commented] (JAMES-3420) WebAdmin request logging should not log password

2020-10-07 Thread Benoit Tellier (Jira)
.com/linagora/james-project/pull/3876 > WebAdmin request logging should not log password > > > Key: JAMES-3420 > URL: https://issues.apache.org/jira/browse/JAMES-3420 > Project: James S

[jira] [Created] (JAMES-3420) WebAdmin request logging should not log password

2020-10-07 Thread Benoit Tellier (Jira)
Benoit Tellier created JAMES-3420: - Summary: WebAdmin request logging should not log password Key: JAMES-3420 URL: https://issues.apache.org/jira/browse/JAMES-3420 Project: James Server

[jira] [Closed] (JAMES-3399) Document structured logging with FluentBit

2020-10-02 Thread Jira
[ https://issues.apache.org/jira/browse/JAMES-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Cordier closed JAMES-3399. --- Fix Version/s: 3.6.0 Resolution: Done > Document structured logging with Fluent

[jira] [Commented] (JAMES-3399) Document structured logging with FluentBit

2020-10-02 Thread Jira
ject/pull/3850] contributed this documentation > Document structured logging with FluentBit > -- > > Key: JAMES-3399 > URL: https://issues.apache.org/jira/browse/JAMES-3399 > Project: James Server

[jira] [Created] (JAMES-3399) Document structured logging with FluentBit

2020-10-01 Thread Benoit Tellier (Jira)
Benoit Tellier created JAMES-3399: - Summary: Document structured logging with FluentBit Key: JAMES-3399 URL: https://issues.apache.org/jira/browse/JAMES-3399 Project: James Server Issue Type

[jira] [Closed] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-07-26 Thread David Leangen (Jira)
[ https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen closed JAMES-3239. > Clarify Logging Configuration (logback.xml & log4j.pro

[jira] [Created] (JAMES-3334) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-07-26 Thread David Leangen (Jira)
David Leangen created JAMES-3334: Summary: Clarify Logging Configuration (logback.xml & log4j.properties) Key: JAMES-3334 URL: https://issues.apache.org/jira/browse/JAMES-3334 Project: James Se

[james-project] 25/31: JAMES-3302 Document logging for the Distributed Server

2020-07-16 Thread btellier
JAMES-3302 Document logging for the Distributed Server --- docs/modules/servers/nav.adoc | 1 + .../servers/pages/distributed/operate/index.adoc | 10 +- .../servers/pages/distributed/operate/logging.adoc | 108 + 3 files changed, 115 insertions(+), 4

[jira] [Commented] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-26 Thread David Leangen (Jira)
have attached the updated logback.xml file for the Basic Server. For some reason, I thought these logs belonged to James, so this issue is effectively invalid. > Reduce logging level of converters to TRACE > --- > >

[jira] [Resolved] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-26 Thread David Leangen (Jira)
[ https://issues.apache.org/jira/browse/JAMES-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen resolved JAMES-3284. -- Resolution: Invalid > Reduce logging level of converters to TR

[jira] [Updated] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-26 Thread David Leangen (Jira)
[ https://issues.apache.org/jira/browse/JAMES-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen updated JAMES-3284: - Attachment: logback.xml > Reduce logging level of converters to TR

[jira] [Commented] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-26 Thread Benoit Tellier (Jira)
ject/pull/225 makes my proposal the default, and addresses other tickets. > Reduce logging level of converters to TRACE > --- > > Key: JAMES-3284 > URL: https://issues.apache.org/jira/browse/JAMES-3284 >

[jira] [Commented] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-26 Thread Benoit Tellier (Jira)
lude INFO / DEBUG log not starting by org.apache.james > Reduce logging level of converters to TRACE > --- > > Key: JAMES-3284 > URL: https://issues.apache.org/jira/browse/JAMES-3284 >

[jira] [Created] (JAMES-3284) Reduce logging level of converters to TRACE

2020-06-25 Thread David Leangen (Jira)
David Leangen created JAMES-3284: Summary: Reduce logging level of converters to TRACE Key: JAMES-3284 URL: https://issues.apache.org/jira/browse/JAMES-3284 Project: James Server Issue Type

[jira] [Resolved] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-25 Thread David Leangen (Jira)
[ https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen resolved JAMES-3239. -- Resolution: Resolved See -JAMES-3251-, which resolves this issue.  > Clarify Logg

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-24 Thread David Leangen (Jira)
the logging system itself at startup. I get the impression that there is something confusing about logging going on here. [~btellier], any thoughts? {noformat} james_1 | 06:28:52,306 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [/opt/apache-james/james-b

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-19 Thread David Leangen (Jira)
rver. So I think concepts like "slf4j" are meaningless. It would, however, be completely appropriate in the Advanced context. > Clarify Logging Configuration (logback.xml & log4j.properties) > -- > >

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-19 Thread Ioan Eugen Stan (Jira)
t is enough: - what framework we are using for logging - slf4j - what is our default logging implementation - link to file - where is the default logging configuration - path in binary distribution - how people can supply their own login configuration - link to slf4j docs - [Advanced] how they can ch

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-18 Thread David Leangen (Jira)
Keep logback What do you mean by "a simple version of it"? How would we do that in practice? > Clarify Logging Configuration (logback.xml & log4j.properties) > -- > > Key: JAMES-323

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-18 Thread Benoit Tellier (Jira)
tune logging. Unability to do so will get them grumpy. IMO we should keep the logback file event for the basic server. Maybe provide a simple version of it. > Clarify Logging Configuration (logback.xml & log4j

[jira] [Commented] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-18 Thread David Leangen (Jira)
t to provide configuration, for the sole reason that (I assume) most Operators are familiar with logging, so it should not be a burden for them to understand. However, depending on how logging is implemented and the way it is supposed to be configured, we may be assuming that they are familiar with

[jira] [Updated] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-18 Thread David Leangen (Jira)
necessary, and if so (2) how can we minimize it and (3) document it better. > Clarify Logging Configuration (logback.xml & log4j.properties) > -- > > Key: JAMES-3239 > URL: https://issues.apa

[jira] [Created] (JAMES-3239) Clarify Logging Configuration (logback.xml & log4j.properties)

2020-06-18 Thread David Leangen (Jira)
David Leangen created JAMES-3239: Summary: Clarify Logging Configuration (logback.xml & log4j.properties) Key: JAMES-3239 URL: https://issues.apache.org/jira/browse/JAMES-3239 Project: James Se

[jira] [Closed] (JAMES-2466) Reduce build logging

2020-06-17 Thread Benoit Tellier (Jira)
. > Reduce build logging > > > Key: JAMES-2466 > URL: https://issues.apache.org/jira/browse/JAMES-2466 > Project: James Server > Issue Type: Improvement > Components: Build System >

[jira] [Closed] (JAMES-2967) Add Logging of IMAP Command

2020-06-17 Thread Benoit Tellier (Jira)
Add Logging of IMAP Command > --- > > Key: JAMES-2967 > URL: https://issues.apache.org/jira/browse/JAMES-2967 > Project: James Server > Issue Type: Improvement > Components: IMAPServer &g

[james-project] branch master updated: JAMES-3221 #comment Improved logging around configuration files for devops

2020-06-17 Thread ieugen
logging around configuration files for devops b90d05e is described below commit b90d05ee7cdd68bb16bb60e6bda1943ba6a89d81 Author: Eugen Stan AuthorDate: Tue Jun 16 12:25:18 2020 +0300 JAMES-3221 #comment Improved logging around configuration files for devops * When loading a

Re: Logging warning

2020-06-15 Thread Eugen Stan
Hi, > The only detail is that in that specific case, we are actually talking > about the CLI tool: we don't really expect a use to choose the logging > library for his CLI. > > And the error is about providing none. > > We can just include a Noop implementation to

Re: Logging warning

2020-06-15 Thread Matthieu Baechler
Hi Eugen, On Mon, 2020-06-15 at 11:13 +0300, Eugen Stan wrote: > Hi, > > Removing the implementation leak a MUST. > > As I've mentioned in the issue/mail, logging implementation is a > deployment decision. I agree > We should provide documentation and make it easy fo

Re: Logging warning

2020-06-15 Thread Eugen Stan
Hi, Removing the implementation leak a MUST. As I've mentioned in the issue/mail, logging implementation is a deployment decision. We should provide documentation and make it easy for people to switch. In a "product like" distribution we will deliver an implementation suitab

Re: Logging warning

2020-06-14 Thread David Leangen
>> When attempting to use the CLI, I encounter this warning: > Very likely we have 2 logging dependencies on the classpath. > > This needs to be rationalised. I will add this to JAMES-3214 as this > relates to cleaning dependency mess… Perfect, thank you! signature.asc De

Re: Logging warning

2020-06-14 Thread Tellier Benoit
Very likely we have 2 logging dependencies on the classpath. This needs to be rationalised. I will add this to JAMES-3214 as this relates to cleaning dependency mess... Cheers, Benoit Le 13/06/2020 à 20:18, David Leangen a écrit : > > Hi! > > For the documentation, I have been t

Logging warning

2020-06-13 Thread David Leangen
Hi! For the documentation, I have been trying to run the “Local” server [1]. [1] https://james.leangen.net/main/3.5/servers/index.html#local When attempting to use the CLI, I encounter this warning: ``` listDomains SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Default

[james-project] 01/04: JAMES-3145 logging org.apache.james.metrics at DEBUG level now logs metrics with a 10 seconds interval

2020-04-27 Thread matthieu
JAMES-3145 logging org.apache.james.metrics at DEBUG level now logs metrics with a 10 seconds interval It allows to have some insights on how the service is performing without the requirement of having a full metrics infrastructure --- .../modules/server

[james-project] 13/39: JAMES-3117 Remove logging in all healthChecks.

2020-04-16 Thread btellier
JAMES-3117 Remove logging in all healthChecks. --- .../james/backends/cassandra/utils/CassandraHealthCheck.java | 6 +- .../org/apache/james/backends/es/ElasticSearchHealthCheck.java | 7 +-- .../apache/james/backends/rabbitmq/RabbitMQHealthCheck.java| 10 ++ .../james/mailbox

[james-project] 18/39: JAMES-3117 Add logging for callers of HealthChecks

2020-04-16 Thread btellier
-3117 Add logging for callers of HealthChecks --- .../org/apache/james/PeriodicalHealthChecks.java | 32 -- .../james/webadmin/routes/HealthCheckRoutes.java | 2 +- 2 files changed, 24 insertions(+), 10 deletions(-) diff --git a/server/container/guice/guice-common/src

[james-project] 15/39: JAMES-3117 Add logging for callers of HealthChecks

2020-04-16 Thread btellier
JAMES-3117 Add logging for callers of HealthChecks --- .../org/apache/james/PeriodicalHealthChecks.java | 32 ++ .../dto/HealthCheckExecutionResultDto.java | 4 +-- .../james/webadmin/routes/HealthCheckRoutes.java | 9 -- 3 files changed, 40 insertions(+), 5

[james-project] 01/09: JAMES-3047 Guice structured logging documentation

2020-02-14 Thread btellier
JAMES-3047 Guice structured logging documentation This documentation was missing. I included a sample file, as well as documentation links of related libraries and softwares. --- src/site/xdoc/server/monitor-logging.xml | 84 1 file changed

[james-project] 06/06: JAMES-2996 Errors upon start should be reported to the logging system

2019-11-28 Thread rcordier
JAMES-2996 Errors upon start should be reported to the logging system log then rethrow pattern is the only solution to do this while still pro- pagating the error. --- .../java/org/apache/james/GuiceJamesServer.java| 23 +++--- 1 file changed, 16 insertions(+), 7

[james-project] 02/10: Fix logging for already created ElasticSearch index

2019-11-24 Thread rcordier
Fix logging for already created ElasticSearch index --- .../java/org/apache/james/backends/es/IndexCreationFactory.java | 2 +- .../src/main/java/org/apache/james/backends/es/IndexName.java| 9 + 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/backends-common

[jira] [Commented] (JAMES-2967) Add Logging of IMAP Command

2019-11-05 Thread Benoit Tellier (Jira)
gt; Add Logging of IMAP Command > --- > > Key: JAMES-2967 > URL: https://issues.apache.org/jira/browse/JAMES-2967 > Project: James Server > Issue Type: Improvement > Components: IMAPServe

[jira] [Created] (JAMES-2967) Add Logging of IMAP Command

2019-11-05 Thread Jerry Malcolm (Jira)
Jerry Malcolm created JAMES-2967: Summary: Add Logging of IMAP Command Key: JAMES-2967 URL: https://issues.apache.org/jira/browse/JAMES-2967 Project: James Server Issue Type: Improvement

[jira] [Closed] (JSPF-105) Rely on slf4j-api for logging

2019-09-30 Thread Benoit Tellier (Jira)
> Rely on slf4j-api for logging > - > > Key: JSPF-105 > URL: https://issues.apache.org/jira/browse/JSPF-105 > Project: James jSPF > Issue Type: Improvement >Reporter: Benoit Telli

[james-jspf] branch master updated: JSPF-105 Rely on slf4j-api for logging

2019-09-30 Thread btellier
logging 6373b7d is described below commit 6373b7d793163f856d0189916af181bd1772a169 Author: Benoit Tellier AuthorDate: Mon Sep 23 12:04:29 2019 +0700 JSPF-105 Rely on slf4j-api for logging --- pom.xml| 10 + resolver/pom.xml

[jira] [Created] (JSPF-105) Rely on slf4j-api for logging

2019-09-22 Thread Tellier Benoit (Jira)
Tellier Benoit created JSPF-105: --- Summary: Rely on slf4j-api for logging Key: JSPF-105 URL: https://issues.apache.org/jira/browse/JSPF-105 Project: James jSPF Issue Type: Improvement

[jira] [Commented] (JSIEVE-112) Use SLF4J & logback for logging

2019-09-15 Thread Rene Cordier (Jira)
ames-jsieve/pull/18 > Use SLF4J & logback for logging > --- > > Key: JSIEVE-112 > URL: https://issues.apache.org/jira/browse/JSIEVE-112 > Project: James jSieve > Issue Type: Improvement >

[jira] [Closed] (JSIEVE-112) Use SLF4J & logback for logging

2019-09-13 Thread Tellier Benoit (Jira)
[ https://issues.apache.org/jira/browse/JSIEVE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JSIEVE-112. - Fix Version/s: 0.6 Resolution: Fixed > Use SLF4J & logback for

[james-jsieve] 05/16: JSIEVE-111 Upgrade commons-logging 1.1.1 -> 1.2

2019-09-13 Thread btellier
JSIEVE-111 Upgrade commons-logging 1.1.1 -> 1.2 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 340cbe4..9a337f0 100644 --- a/pom.xml +++ b/pom.xml @@ -130,7 +130,7 @@ commons-logging comm

[james-jsieve] 16/16: JSIEVE-112 Replace commons-logging by slf4j

2019-09-13 Thread btellier
JSIEVE-112 Replace commons-logging by slf4j --- core/pom.xml | 4 +- .../java/org/apache/jsieve/BaseSieveContext.java | 18 +- core/src/main/java/org/apache/jsieve/Command.java | 14 ++--- .../org/apache/jsieve/ConfigurationManager.java| 28

[jira] [Created] (JSIEVE-112) Use SLF4J & logback for logging

2019-09-09 Thread Tellier Benoit (Jira)
Tellier Benoit created JSIEVE-112: - Summary: Use SLF4J & logback for logging Key: JSIEVE-112 URL: https://issues.apache.org/jira/browse/JSIEVE-112 Project: James jSieve Issue

[james-mime4j] 05/13: MIME4J-289 Upgrade common-logging 1.1.1 -> 1.2

2019-09-08 Thread btellier
MIME4J-289 Upgrade common-logging 1.1.1 -> 1.2 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index b45b5d5..ba6a845 100644 --- a/pom.xml +++ b/pom.xml @@ -69,7 +69,7 @@ 1.8 1.8 -1.1.1 +1.2 1.2

[james-jdkim] 05/18: JDKIM-42 Upgrade commons-logging 1.1.1 -> 1.2

2019-09-08 Thread btellier
JDKIM-42 Upgrade commons-logging 1.1.1 -> 1.2 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index a054c24..952d22a 100644 --- a/pom.xml +++ b/pom.xml @@ -66,7 +66,7 @@ 1.1 1.8.3 1.13 -1.1.1 +

[james-project] 09/23: JAMES-2097 Logging for MockSMTP server

2019-09-05 Thread btellier
JAMES-2097 Logging for MockSMTP server --- server/mailet/mock-smtp-server/pom.xml | 5 + .../james/mock/smtp/server/MockMessageHandler.java | 11 +-- .../mailet/mock-smtp-server/src/resources/logback.xml | 18 ++ 3 files changed, 32 insertions

[james-project] branch master updated: JAMES-2821 memory product should use logback for logging

2019-07-09 Thread matthieu
should use logback for logging new 6a87529 Merge branch 'pr-2507' 300eb24 is described below commit 300eb247750641c4d28d8de93ff5f952e43ba0fe Author: Matthieu Baechler AuthorDate: Mon May 13 16:22:29 2019 +0200 JAMES-2821 memory product should use logback for logging --- server

[james-project] 03/03: Merge remote-tracking branch 'mbaechler/fix-es-logging'

2019-06-21 Thread rouazana
15:16:23 2019 +0200 Merge remote-tracking branch 'mbaechler/fix-es-logging' backends-common/elasticsearch/pom.xml | 6 ++ 1 file changed, 6 insertions(+) - To unsubscribe, e-mail: server-de

[james-project] 01/03: JAMES-2767 prevent import of commons-logging to make log go through slf4j

2019-06-21 Thread rouazana
JAMES-2767 prevent import of commons-logging to make log go through slf4j --- backends-common/elasticsearch/pom.xml | 6 ++ 1 file changed, 6 insertions(+) diff --git a/backends-common/elasticsearch/pom.xml b/backends-common/elasticsearch/pom.xml index 7f92990..20122f6 100644 --- a

[james-project] 05/09: JAMES-2671 Avoid pulling commons-logging along with AWS SDK

2019-06-04 Thread btellier
JAMES-2671 Avoid pulling commons-logging along with AWS SDK --- server/blob/blob-objectstorage/pom.xml | 10 ++ 1 file changed, 10 insertions(+) diff --git a/server/blob/blob-objectstorage/pom.xml b/server/blob/blob-objectstorage/pom.xml index b9975bb..a92e073 100644 --- a/server/blob

[jira] [Closed] (MAILBOX-254) Don't depends on commons-logging in HBase

2019-05-19 Thread Tellier Benoit (JIRA)
> Don't depends on commons-logging in HBase > - > > Key: MAILBOX-254 > URL: https://issues.apache.org/jira/browse/MAILBOX-254 > Project: James Mailbox > Issue Type: Bug &g

[james-project] 02/07: JAMES-2233 Correlate request and response logging using a requestId

2019-05-09 Thread btellier
JAMES-2233 Correlate request and response logging using a requestId --- .../james/webadmin/mdc/LoggingRequestFilter.java | 6 ++ .../james/webadmin/mdc/LoggingResponseFilter.java | 4 ++ .../{LoggingRequestFilter.java => RequestId.java} | 67 ++ .../apache/james/webad

[jira] [Resolved] (JAMES-2731) MailboxPath logging should not rely on getFullName

2019-04-10 Thread Tellier Benoit (JIRA)
> MailboxPath logging should not rely on getFullName > -- > > Key: JAMES-2731 > URL: https://issues.apache.org/jira/browse/JAMES-2731 > Project: James Server > Issue Type: Improvement

[jira] [Closed] (JAMES-2731) MailboxPath logging should not rely on getFullName

2019-04-10 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2731. - > MailboxPath logging should not rely on getFullN

[jira] [Created] (JAMES-2731) MailboxPath logging should not rely on getFullName

2019-04-09 Thread Tellier Benoit (JIRA)
Tellier Benoit created JAMES-2731: - Summary: MailboxPath logging should not rely on getFullName Key: JAMES-2731 URL: https://issues.apache.org/jira/browse/JAMES-2731 Project: James Server

[jira] [Closed] (JAMES-2670) Clean mailbox provisioning logging

2019-03-01 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2670. - > Clean mailbox provisioning logging > -- > >

[jira] [Resolved] (JAMES-2670) Clean mailbox provisioning logging

2019-03-01 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JAMES-2670. --- Resolution: Fixed > Clean mailbox provisioning logg

[jira] [Commented] (JAMES-2670) Clean mailbox provisioning logging

2019-03-01 Thread Tellier Benoit (JIRA)
ject/pull/2196 did improve this > Clean mailbox provisioning logging > -- > > Key: JAMES-2670 > URL: https://issues.apache.org/jira/browse/JAMES-2670 > Project: James Server >

[james-project] 04/04: JAMES-2670 Clean mailbox provisioning logging

2019-03-01 Thread btellier
JAMES-2670 Clean mailbox provisioning logging --- .../java/org/apache/james/imap/processor/AbstractAuthProcessor.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/protocols/imap/src/main/java/org/apache/james/imap/processor/AbstractAuthProcessor.java b/protocols

[jira] [Created] (JAMES-2673) Monitoring via logging document is out-of-date

2019-02-27 Thread Gautier DI FOLCO (JIRA)
Gautier DI FOLCO created JAMES-2673: --- Summary: Monitoring via logging document is out-of-date Key: JAMES-2673 URL: https://issues.apache.org/jira/browse/JAMES-2673 Project: James Server

[jira] [Created] (JAMES-2670) Clean mailbox provisioning logging

2019-02-26 Thread Gautier DI FOLCO (JIRA)
Gautier DI FOLCO created JAMES-2670: --- Summary: Clean mailbox provisioning logging Key: JAMES-2670 URL: https://issues.apache.org/jira/browse/JAMES-2670 Project: James Server Issue Type

[12/12] james-project git commit: JAMES-2630 Improve Cassandra logging

2019-01-28 Thread matthieu
JAMES-2630 Improve Cassandra logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/e061ccb5 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/e061ccb5 Diff: http://git-wip-us.apache.org/repos

[09/13] james-project git commit: MAILBOX-376 Structured logging for event dispatching

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for event dispatching Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/a25a1c66 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/a25a1c66 Diff: http://git-wip

[07/13] james-project git commit: MAILBOX-376 Structured logging for local mailbox listener execution

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for local mailbox listener execution Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/10d49b51 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/10d49b51 Diff: http

[06/13] james-project git commit: MAILBOX-376 Structured logging for InVmEventDelivery

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for InVmEventDelivery Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/97b33f80 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/97b33f80 Diff: http://git-wip

[05/13] james-project git commit: MAILBOX-376 Structured logging for group listener execution

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for group listener execution Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/e3072f26 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/e3072f26 Diff: http://git

[08/13] james-project git commit: MAILBOX-376 Structured logging for groups retries

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for groups retries Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/c70c9871 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/c70c9871 Diff: http://git-wip

[12/13] james-project git commit: MAILBOX-376 Structured logging for key registrations

2019-01-23 Thread btellier
MAILBOX-376 Structured logging for key registrations Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/dbc54427 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/dbc54427 Diff: http://git-wip

[7/7] james-project git commit: JAMES-2611 Use info level for logging when managesieve.xml is missing

2018-12-18 Thread rouazana
JAMES-2611 Use info level for logging when managesieve.xml is missing Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/ab977196 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/ab977196 Diff

[5/7] james-project git commit: JAMES-2611 Add Logging level parameterization for ConfigurationProvider

2018-12-18 Thread rouazana
JAMES-2611 Add Logging level parameterization for ConfigurationProvider Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/e57655f9 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/e57655f9 Diff

[3/7] james-project git commit: JAMES-2611 Use info level for logging when lmtpserver.xml is missing

2018-12-18 Thread rouazana
JAMES-2611 Use info level for logging when lmtpserver.xml is missing Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/5fb15251 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/5fb15251 Diff: http

[4/5] james-project git commit: JAMES-2457 Turn request logging off when testing large mail

2018-08-26 Thread btellier
JAMES-2457 Turn request logging off when testing large mail This consume significant amount of memory and do not affect correctness Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/52cde217 Tree: http://git

[14/24] james-project git commit: JAMES-2493 try to drop commons-logging

2018-07-30 Thread btellier
JAMES-2493 try to drop commons-logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/2135e5ee Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/2135e5ee Diff: http://git-wip-us.apache.org/repos

[06/11] james-project git commit: JAMES-2466 Turn logback logging level to WARN in tests

2018-07-12 Thread rouazana
JAMES-2466 Turn logback logging level to WARN in tests Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/5dab030a Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/5dab030a Diff: http://git-wip

[jira] [Created] (JAMES-2466) Reduce build logging

2018-07-11 Thread Tellier Benoit (JIRA)
Tellier Benoit created JAMES-2466: - Summary: Reduce build logging Key: JAMES-2466 URL: https://issues.apache.org/jira/browse/JAMES-2466 Project: James Server Issue Type: Improvement

[16/17] james-project git commit: JAMES-2334 Improve rabbit mq image logging

2018-05-31 Thread matthieu
JAMES-2334 Improve rabbit mq image logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/c7d08bb7 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/c7d08bb7 Diff: http://git-wip-us.apache.org

[04/15] james-project git commit: JAMES-2368 Improve logging message

2018-05-03 Thread btellier
JAMES-2368 Improve logging message Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/3f52de9a Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/3f52de9a Diff: http://git-wip-us.apache.org/repos/asf

[3/6] james-project git commit: JAMES-2378 Enforce immutable list usage when logging

2018-04-27 Thread btellier
JAMES-2378 Enforce immutable list usage when logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/7d80a4c2 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/7d80a4c2 Diff: http://git-wip

[23/24] james-project git commit: JAMES-2381 Improve an ambiguous logging message in RRT processors

2018-04-25 Thread matthieu
JAMES-2381 Improve an ambiguous logging message in RRT processors Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/080ba116 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/080ba116 Diff: http

[4/9] james-project git commit: MAILBOX-325 Logging failed transactions

2018-03-23 Thread btellier
MAILBOX-325 Logging failed transactions Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/336d1f94 Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/336d1f94 Diff: http://git-wip-us.apache.org

[jira] [Closed] (JAMES-2085) Review logging in depth in James code

2018-01-28 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit closed JAMES-2085. - > Review logging in depth in James c

[jira] [Resolved] (JAMES-2085) Review logging in depth in James code

2018-01-28 Thread Tellier Benoit (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit resolved JAMES-2085. --- Resolution: Fixed > Review logging in depth in James c

[44/50] [abbrv] james-project git commit: JAMES-2199 Guard potentially expensive logging by checks that logging at the specified levels is enabled

2017-12-18 Thread aduprat
JAMES-2199 Guard potentially expensive logging by checks that logging at the specified levels is enabled Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/8df44251 Tree: http://git-wip-us.apache.org/repos/asf

[29/50] [abbrv] james-project git commit: JAMES-2199 Switch to parameterized logging

2017-12-18 Thread aduprat
JAMES-2199 Switch to parameterized logging Also, this merges recipientString calculation into the logger call, as toString() is called automatically: https://www.slf4j.org/faq.html#string_contents Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip

[28/50] [abbrv] james-project git commit: JAMES-2199 Switch to parameterized logging

2017-12-18 Thread aduprat
JAMES-2199 Switch to parameterized logging Also removed the call to StringUtils.arrayToString() Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/f901f05e Tree: http://git-wip-us.apache.org/repos/asf/james

[39/50] [abbrv] james-project git commit: JAMES-2199 Remove is*Enabled() checks and switch to parameterized logging

2017-12-18 Thread aduprat
http://git-wip-us.apache.org/repos/asf/james-project/blob/04657f2d/server/mailet/mailets/src/main/java/org/apache/james/transport/mailets/jsieve/RedirectAction.java -- diff --git a/server/mailet/mailets/src/main/java/org/apache/ja

[32/50] [abbrv] james-project git commit: JAMES-2199 Switch to parameterized logging

2017-12-18 Thread aduprat
JAMES-2199 Switch to parameterized logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/4266f0fb Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/4266f0fb Diff: http://git-wip-us.apache.org

[40/50] [abbrv] james-project git commit: JAMES-2199 Remove is*Enabled() checks and switch to parameterized logging

2017-12-18 Thread aduprat
JAMES-2199 Remove is*Enabled() checks and switch to parameterized logging Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/04657f2d Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/04657f2d Diff

  1   2   3   4   >