[MAGNOLIA-3999] Current logs are pretty crowded - we should analyze the content and eliminate the unwanted ones Created: 06/Mar/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5
Fix Version/s: 4.5.x

Type: Task Priority: Neutral
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-3691 Remove incorrect warnings Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Warnings: these should be fixed - there should be no warnings e.g. on demo-project
Info: some of them should actually use level debug -> they would not show up unless logging config was changed



 Comments   
Comment by Daniel Lipp [ 07/Mar/12 ]

most of the warnings would be eliminated with fixing the issue linked here

Comment by Michael Mühlebach [ 02/Aug/16 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an old version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

Generated at Mon Feb 12 03:51:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.