...
| Attribute name | Description | Allowed values | Default | ||
|---|---|---|---|---|---|
| Pattern for generating the output file name. | Valid path to log file name. The file name is normalized as much as possible. | %h/java%u.log | ||
level | Specifies the logging level. In general there are logged just messages with the same or higher priority than the level specified. The level SEVERE has the highest priority, FINEST the lowest one. |
| INFO | ||
filter | Specifies the name of a Filter class to use (defaults to no Filter). | Fully qualified Java class name. | (no filter) | ||
encoding | The name of the character set encoding to use. | Valid Java character set name. Example: like UTF-8 | (platform encoding) | ||
limit | Specifies an approximate maximum amount to write (in bytes) to any one file. If this is zero, then there is no limit. | Integer value >= 0 | (no limit) | ||
count | Specifies how many output files to cycle through. This allows you to maintain a limited number of log file archives with a maximum size specified by the limit attribute (rolling log files). | Integer value >= 1 | 1 | ||
append | Specifies whether the FileHandler should append onto any existing files. | true | false | false | ||
mkdirs | Specifies whether the installer should recursively create the parent directory of the log file speciified by the
| true | false | false |
Alternatively, to savor the full flavour of Java Logging there can be passed a configuration properties file. This allows the user to define his/her own set of handlers and formatters on different Java package levels. For example there might be used different log files for IZPack and for a business implementation plugging in to IzPack.
...