[
https://issues.apache.org/jira/browse/JCR-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116217#comment-17116217
]
Julian Reschke edited comment on JCR-4169 at 5/26/20, 9:51 AM:
---------------------------------------------------------------
[~reschke], see [^JCR-4169.patch]. Added RFC4918IfHeaderTest as known issue,
I'll open separate issues for that.
Patch contains:
* Trivial changes to existing WebDAV tests.
* Moved server tests from jackrabbit-webdav to jackrabbit jcr-server to avoid a
cyclic dependency.
* Made server tests start their own WebDAV server.
* Added connection handling
* Marked RFC4918IfHeaderTest as known failure because actually there are issues
with the If -Header treatment of the WebDAV servlets.
was (Author: baedke):
[~reschke], see JCR-4169.patch. Added RFC4918IfHeaderTest as known issue, I'll
open separate issues for that.
Patch contains:
* Trivial changes to existing WebDAV tests.
* Moved server tests from jackrabbit-webdav to jackrabbit jcr-server to avoid a
cyclic dependency.
* Made server tests start their own WebDAV server.
* Added connection handling
* Marked RFC4918IfHeaderTest as known failure because actually there are issues
with the If -Header treatment of the WebDAV servlets.
> make WebdavServerTests run automatically
> ----------------------------------------
>
> Key: JCR-4169
> URL: https://issues.apache.org/jira/browse/JCR-4169
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-server
> Reporter: Julian Reschke
> Assignee: Manfred Baedke
> Priority: Minor
> Attachments: JCR-4158-prelimary.patch, JCR-4169.patch
>
>
> These tests aren't currently run automatically, as they require a separate
> jackrabbit-standalone instance running.
> Consider starting this up as part of the test fixture.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
