You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/06/18 05:07:00 UTC
[jira] [Closed] (JAMES-2466) Reduce build logging
[ https://issues.apache.org/jira/browse/JAMES-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-2466.
---------------------------------
Resolution: Fixed
The build log size are now way smaller, this likely is no longer an issue.
> Reduce build logging
> --------------------
>
> Key: JAMES-2466
> URL: https://issues.apache.org/jira/browse/JAMES-2466
> Project: James Server
> Issue Type: Improvement
> Components: Build System
> Reporter: Benoit Tellier
> Priority: Major
>
> When building James, we currently generate a ~200MB file of logs.
> This is too much: downloading it is long, analysing it is complicated and storing it is costly.
> Hence, as we don't care about detailed logs, and as we can easily turn logging level higher when debugging, I'd like to suggest enforcing WARN logging level for test in projects using *logback*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org