[MAGNOLIA-2001] Redundant and unused log4j.dtd files Created: 14/Jan/08  Updated: 23/Jan/13  Resolved: 18/Feb/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.3
Fix Version/s: 3.5.4

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2036 Check log4j warnings on startup Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

There are redundant log4j.dtd files in core and magnolia-empty-webapp; they are not used, and the original dtd is in the log4j jar.



 Comments   
Comment by Magnolia International [ 14/Jan/08 ]

removed the DTDs, added namespace declarations to log4j.xml files

Comment by Magnolia International [ 23/Jan/08 ]

I'm getting warnings in the logs.. to be checked.

log4j:WARN Continuable parsing error 29 and column 23
log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,appender*,(category|logger)*,root?,categoryFactory?)".

Comment by Magnolia International [ 01/Feb/08 ]

will check these warnings in MAGNOLIA-2036

Comment by Philipp Bracher [ 18/Feb/08 ]

I get the messages on a freshly installed EE 3.5.4

Comment by Philipp Bracher [ 18/Feb/08 ]

sorry didn't check MAGNOLIA-2036

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