Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12.12, 1.13.3
-
None
-
None
Description
Current Situation:
- When the LogFile settings are configured:
- YADE always adjusts programmatically the filePattern of the log4j2 configuration for a RollingFile (JadeReportLogAppender from the log4j2.xml) to create a gz file.
- YADE changes programmatically the default filePattern of the log4j2.xml configuration:
- filePattern="<tmp directory path>/YADE-%d{yyyy-MM-dd}.log" to
- filePattern="<LogFile>.%d{yyyy-MM}-%i.gz"
- The changed pattern %d{yyyy-MM}-%i.gz is completely different to the configured %d{yyyy-MM-dd}.log pattern to create the archive files.
- YADE changes programmatically the default filePattern of the log4j2.xml configuration:
- Example:
- YADE configuration <LogFile>:
- C:/tmp/my_yade.log
- changed filePattern is:
- filePattern="C:/tmp/my_yade.log.%d{yyyy-MM}-%i.gz"
- but like the default filePattern, the changed filePattern should be:
- filePattern="C:/tmp/my_yade.log.%d{yyyy-MM-dd}.log"
- but like the default filePattern, the changed filePattern should be:
- filePattern="C:/tmp/my_yade.log.%d{yyyy-MM}-%i.gz"
- YADE configuration <LogFile>:
- YADE always adjusts programmatically the filePattern of the log4j2 configuration for a RollingFile (JadeReportLogAppender from the log4j2.xml) to create a gz file.
Desired Behavior:
- YADE should only replace the file name (${env:TEMP}/YADE-) of the default filePattern with <LogFile> and not recreate the configured filePattern completely.
- the default filePattern should be extended to support the SizeBasedTriggeringPolicy (must contain a %i)
- filePattern="<tmp directory path>/YADE-%d{yyyy-MM-dd}-%i.log"