[
https://issues.apache.org/jira/browse/JCRVLT-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-573:
-----------------------------------
Description: Instead of using log4j
(https://github.com/apache/jackrabbit-filevault/blob/b94a474e40dd229b047ec0c33fc3ac53dfc3d8a5/vault-cli/pom.xml#L176-L180)
which reached EOL in 2015 we should switch to [Logback|http://logback.qos.ch/]
as native implementation of SLF4J. That also eases adjusting the log
configuration without patching the VLT CLI jar file. (was: Instead of using
the log4j
(https://github.com/apache/jackrabbit-filevault/blob/b94a474e40dd229b047ec0c33fc3ac53dfc3d8a5/vault-cli/pom.xml#L176-L180)
which reached EOL in 2015 we should switch to [Logback|http://logback.qos.ch/]
as native implementation of SLF4J. That also eases adjusting the log level
without patching the VLT CLI package.)
> Use Logback for logging with CLI
> --------------------------------
>
> Key: JCRVLT-573
> URL: https://issues.apache.org/jira/browse/JCRVLT-573
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.5.8
>
>
> Instead of using log4j
> (https://github.com/apache/jackrabbit-filevault/blob/b94a474e40dd229b047ec0c33fc3ac53dfc3d8a5/vault-cli/pom.xml#L176-L180)
> which reached EOL in 2015 we should switch to
> [Logback|http://logback.qos.ch/] as native implementation of SLF4J. That also
> eases adjusting the log configuration without patching the VLT CLI jar file.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
