[ 
https://issues.apache.org/jira/browse/JCRVLT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676878#comment-17676878
 ] 

Konrad Windszus commented on JCRVLT-677:
----------------------------------------

The logger should rely on the default SLF4J formatting options instead of 
trying to format individually with the helper method {{addCause()}} 
(https://github.com/apache/jackrabbit-filevault/blob/39b4463904719a423a3ebe000b049b0653557591/vault-cli/src/main/java/org/apache/jackrabbit/vault/util/console/ExecutionContext.java#L146)

> NPE during "vlt checkout"
> -------------------------
>
>                 Key: JCRVLT-677
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-677
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>    Affects Versions: 3.6.8
>            Reporter: Konrad Windszus
>            Priority: Major
>
> When executing {{vlt co}} against the root of an existing repository the 
> following error is thrown:
> {code}
> vlt --credentials admin:admin co http://localhost:4502 --force -v
> Checkout http://localhost:4502/crx/server/-/jcr:root/ with local files using 
> root at /Users/konradwindszus/CQ-Server-Export/AEMCloud/jcr_root
> Connecting via JCR remoting to http://localhost:4502/crx/server
> [WARN ] Credentials for http://localhost:4502/crx/server/-/jcr:root/ updated 
> in /Users/konradwindszus/.vault/auth.xml.
> Filter
> `-- NodeFilterSet
>     |-- root: /, mode REPLACE
>     |-- exclude
>     |   `-- DefaultPathFilter:
>     |       `-- regex: /jcr:system
>     |-- exclude
>     |   `-- DefaultPathFilter:
>     |       `-- regex: /var/classes
>     `-- exclude
>         `-- DefaultPathFilter:
>             `-- regex: ^.*/rep:accessControl
> `-- PropertyFilterSet
>     |-- root: /, mode REPLACE
> Checking out / to jcr_root
> [ERROR] checkout: java.lang.NullPointerException: null
> {code}
> The stack trace is never exposed even with DEBUG category enabled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to