[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Fix Version/s: 2.14.9
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.19.5, 2.18.4, 2.16.6, 2.14.9
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Labels: candidate_jcr_2_12 (was: candidate_jcr_2_14)
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_12
> Fix For: 2.20, 2.19.5, 2.18.4, 2.16.6, 2.14.9
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16)
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.19.5, 2.18.4, 2.16.6
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Fix Version/s: 2.16.6
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_16
> Fix For: 2.20, 2.19.5, 2.18.4, 2.16.6
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Labels: candidate_jcr_2_16 (was: candidate_jcr_2_18)
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_16
> Fix For: 2.20, 2.19.5, 2.18.4
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Fix Version/s: 2.18.4
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_18
> Fix For: 2.20, 2.19.5, 2.18.4
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4475:
Labels: candidate_jcr_2_18 (was: )
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Labels: candidate_jcr_2_18
> Fix For: 2.20, 2.19.5
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4475:
Attachment: servlet_path_prefix2.patch
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: servlet_path_prefix.patch, servlet_path_prefix2.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4475:
Description:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=1. Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=2. With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=3. With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=4. With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
{noformat:title=5. With custom context path and custom servlet path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
-DWebDAVServletPrefix="/jcrserver"
{noformat}
was:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=1. Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=2. With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=3. With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=4. With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
{noformat:title=5. With custom context path and custom servlet path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
-DWebDAVServletPrefix="/jcrserver"
{noformat}
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: servlet_path_prefix.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4475:
Description:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=1. Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=2. With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=3. With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=4. With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
{noformat:title=5. With custom context path and custom servlet path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
-DWebDAVServletPrefix="/jcrserver"
{noformat}
was:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
{noformat:title=With custom context path and custom servlet path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
-DWebDAVServletPrefix="/jcrserver"
{noformat}
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Priority: Major
> Fix For: 2.20
>
> Attachments: servlet_path_prefix.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=1. Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=2. With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=3. With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=4. With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=5. With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4475:
Description:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
{noformat:title=With custom context path and custom servlet path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
-DWebDAVServletPrefix="/jcrserver"
{noformat}
was:
{{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
custom context path like the following, but not with custom servlet path
mapping.
{noformat}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
{noformat}
It would be nice if we can test with custom servlet path mapping as well,
instead of the hard-coded "/server" path only, like the following examples:
{noformat:title=Default with /server prefix}
$ mvn clean install -PintegrationTesting
{noformat}
{noformat:title=With empty servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
{noformat}
{noformat:title=With custom servlet path prefix}
mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
{noformat}
{noformat:title=With custom context path}
mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
{noformat}
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Priority: Major
> Fix For: 2.20
>
> Attachments: servlet_path_prefix.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
> {noformat:title=With custom context path and custom servlet path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> -DWebDAVServletPrefix="/jcrserver"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4475) Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path mapping
[
https://issues.apache.org/jira/browse/JCR-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4475:
Attachment: servlet_path_prefix.patch
> Improve o.a.j.jcr2dav.RepositoryStubImpl to test with custom servlet path
> mapping
> -
>
> Key: JCR-4475
> URL: https://issues.apache.org/jira/browse/JCR-4475
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Woonsan Ko
>Priority: Major
> Fix For: 2.20
>
> Attachments: servlet_path_prefix.patch
>
>
> {{org.apache.jackrabbit.jcr2dav.RepositoryStubImpl}} supports testing with
> custom context path like the following, but not with custom servlet path
> mapping.
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
> It would be nice if we can test with custom servlet path mapping as well,
> instead of the hard-coded "/server" path only, like the following examples:
> {noformat:title=Default with /server prefix}
> $ mvn clean install -PintegrationTesting
> {noformat}
> {noformat:title=With empty servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix=""
> {noformat}
> {noformat:title=With custom servlet path prefix}
> mvn clean install -PintegrationTesting -DWebDAVServletPrefix="/jcrserver"
> {noformat}
> {noformat:title=With custom context path}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foo"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
