[
https://issues.apache.org/jira/browse/JCRVLT-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566329#comment-17566329
]
Konrad Windszus commented on JCRVLT-644:
----------------------------------------
The commit
https://github.com/apache/jackrabbit-filevault/commit/4590f8f71b01e51fe2faaec26f86fa5af2a5c8e8#diff-4e9c587208abb465e3c93af5e8b6868f0b8b8e09b6dc5fd48e0b8b658b2f3cf3R462
only changed the {{isStrict}} flag used in ITs by default from {{false}} to
{{true}}. However, a modified test with explicit {{setStrict(false)}} on the
used {{ImportOptions}} still fails in master, so it seems another subsequent
commit is the culprit.
> import of package with not well-formed DocViews behaves differently since
> 3.5.2
> -------------------------------------------------------------------------------
>
> Key: JCRVLT-644
> URL: https://issues.apache.org/jira/browse/JCRVLT-644
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Julian Reschke
> Assignee: Konrad Windszus
> Priority: Major
>
> It appears that the behavior for packages containing broken content.xml
> entries changed in (ca.) version 3.5.2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
