[
https://issues.apache.org/jira/browse/JCRVLT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688245#comment-16688245
]
Konrad Windszus edited comment on JCRVLT-323 at 11/30/18 12:53 PM:
-------------------------------------------------------------------
Now JCR-4120 is finally fixed. To fix this issue as well the next FileVault
release should just upgrade to the (not yet released) version 2.18 of
jackrabbit-spi2dav and in addition remove the workaround of hardcoding the
workspace name in
https://github.com/apache/jackrabbit-filevault/blob/01737d7a91e06a58895aa365a15a0047dc7f6b49/vault-davex/src/main/java/org/apache/jackrabbit/vault/davex/DAVExRepositoryFactory.java#L107.
was (Author: kwin):
Now JCR-4120 is finally fixed. To fix this issue as well the next FileVault
release should just upgrade to the (not yet released) version 2.18 of
jackrabbit-spi2dav.
> Unable to perform sync due to wrong default workspace handling
> --------------------------------------------------------------
>
> Key: JCRVLT-323
> URL: https://issues.apache.org/jira/browse/JCRVLT-323
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.1.38
> Reporter: Konrad Windszus
> Priority: Major
>
> This issue is similar to JCRVLT-144 but it happens while performing the
> {{sync}} instead of {{checkout}}. Please fix this as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
