[jira] [Assigned] (JCRVLT-360) Add equals and toString methods to DefaultWorkspaceFilter
[ https://issues.apache.org/jira/browse/JCRVLT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned JCRVLT-360: -- Component/s: vlt Assignee: Konrad Windszus Summary: Add equals and toString methods to DefaultWorkspaceFilter (was: Add equals and toString methods to DocViewNode and DocViewProperty) > Add equals and toString methods to DefaultWorkspaceFilter > - > > Key: JCRVLT-360 > URL: https://issues.apache.org/jira/browse/JCRVLT-360 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (JCRVLT-360) Add equals and toString methods to DocViewNode and DocViewProperty
Konrad Windszus created JCRVLT-360: -- Summary: Add equals and toString methods to DocViewNode and DocViewProperty Key: JCRVLT-360 URL: https://issues.apache.org/jira/browse/JCRVLT-360 Project: Jackrabbit FileVault Issue Type: Improvement Reporter: Konrad Windszus -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCRVLT-360) Add equals and toString methods to DefaultWorkspaceFilter and FilterSet
[ https://issues.apache.org/jira/browse/JCRVLT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-360: --- Summary: Add equals and toString methods to DefaultWorkspaceFilter and FilterSet (was: Add equals and toString methods to DefaultWorkspaceFilter) > Add equals and toString methods to DefaultWorkspaceFilter and FilterSet > --- > > Key: JCRVLT-360 > URL: https://issues.apache.org/jira/browse/JCRVLT-360 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4458) When JcrRemotingServlet deployed on non-root context, AclResource Webdav request fails
[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4458:
Fix Version/s: 2.20
> When JcrRemotingServlet deployed on non-root context, AclResource Webdav
> request fails
> --
>
> Key: JCR-4458
> URL: https://issues.apache.org/jira/browse/JCR-4458
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.18.2
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
>
> If {{org.apache.jackrabbit.server.remoting.davex.JcrRemotingServlet}} is
> configured in a non-root web application, the contextPath of which is "/cms"
> for example with the servletPath, "/server", then
> {{javax.jcr.Session#importXML(...)}} fails from a JCR client based on
> JCR/WebDAV. In other words, {{#importXML(...)}} fails from a JCR {{Session}}
> using a repository which can be created like the following for JCR over
> WebDAV:
> {code}
> String repositoryAddress = "http://localhost:8080/cms/server;;
> Jcr2davRepositoryFactory factory = new Jcr2davRepositoryFactory();
> Map params = new HashMap();
> params.put(JcrUtils.REPOSITORY_URI, repositoryAddress);
> Repository repository = factory.getRepository(params);
> // ...
> {code}
> It seems like that {{Session#importXML(...)}} call invokes an AclResource
> Webdav request first on the specific resource path, but
> {{org.apache.jackrabbit.webdav.jcr.version.report.JcrPrivilegeReport#init(DavResource,
> ReportInfo)}} does not remove the contextPath, "/cms" for example, when
> determining the resoucrePath.
> Unlike the {{JcrPrivilegeReport}},
> {{org.apache.jackrabbit.webdav.WebdavRequestImpl#getHrefLocator(String,
> boolean)}} seems to remove the contextPath properly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCRVLT-360) Add equals and toString methods to DefaultWorkspaceFilter and FilterSet
[ https://issues.apache.org/jira/browse/JCRVLT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-360: --- Fix Version/s: 3.2.10 Status: Patch Available (was: In Progress) I provided a fix in https://github.com/apache/jackrabbit-filevault/pull/55. [~tripod] Can you have a look? > Add equals and toString methods to DefaultWorkspaceFilter and FilterSet > --- > > Key: JCRVLT-360 > URL: https://issues.apache.org/jira/browse/JCRVLT-360 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.2.10 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4437) Update Tika dependency to 1.21
[ https://issues.apache.org/jira/browse/JCR-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843759#comment-16843759 ] Julian Reschke edited comment on JCR-4437 at 8/29/19 1:49 PM: -- trunk: (2.19.4) [r1859534|http://svn.apache.org/r1859534] 2.18: (2.18.3) [r1863250|http://svn.apache.org/r1863250] 2.16: [r1866073|http://svn.apache.org/r1866073] was (Author: reschke): trunk: [r1859534|http://svn.apache.org/r1859534] 2.18: [r1863250|http://svn.apache.org/r1863250] > Update Tika dependency to 1.21 > -- > > Key: JCR-4437 > URL: https://issues.apache.org/jira/browse/JCR-4437 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848774#comment-16848774 ] Julian Reschke edited comment on JCR-4441 at 8/29/19 2:27 PM: -- trunk: (2.19.4) [r1860118|http://svn.apache.org/r1860118] 2.18: (2.18.3) [r1863252|http://svn.apache.org/r1863252] 2.16: [r1866076|http://svn.apache.org/r1866076] was (Author: reschke): trunk: [r1860118|http://svn.apache.org/r1860118] 2.18: [r1863252|http://svn.apache.org/r1863252] > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4442) Update animal-sniffer dependency to 1.18
[ https://issues.apache.org/jira/browse/JCR-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848868#comment-16848868 ] Julian Reschke edited comment on JCR-4442 at 8/29/19 2:47 PM: -- trunk: (2.19.4) [r1860123|http://svn.apache.org/r1860123] 2.18: (2.18.3) [r1863253|http://svn.apache.org/r1863253] 2.16: [r1866077|http://svn.apache.org/r1866077] was (Author: reschke): trunk: [r1860123|http://svn.apache.org/r1860123] 2.18: [r1863253|http://svn.apache.org/r1863253] > Update animal-sniffer dependency to 1.18 > > > Key: JCR-4442 > URL: https://issues.apache.org/jira/browse/JCR-4442 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCR-4458) When JcrRemotingServlet deployed on non-root context, AclResource Webdav request fails
[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918588#comment-16918588
]
Julian Reschke commented on JCR-4458:
-
in svn patch format: [^JCR-4458.diff] - tests pass for me
> When JcrRemotingServlet deployed on non-root context, AclResource Webdav
> request fails
> --
>
> Key: JCR-4458
> URL: https://issues.apache.org/jira/browse/JCR-4458
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.18.2
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: JCR-4458.diff
>
>
> If {{org.apache.jackrabbit.server.remoting.davex.JcrRemotingServlet}} is
> configured in a non-root web application, the contextPath of which is "/cms"
> for example with the servletPath, "/server", then
> {{javax.jcr.Session#importXML(...)}} fails from a JCR client based on
> JCR/WebDAV. In other words, {{#importXML(...)}} fails from a JCR {{Session}}
> using a repository which can be created like the following for JCR over
> WebDAV:
> {code}
> String repositoryAddress = "http://localhost:8080/cms/server;;
> Jcr2davRepositoryFactory factory = new Jcr2davRepositoryFactory();
> Map params = new HashMap();
> params.put(JcrUtils.REPOSITORY_URI, repositoryAddress);
> Repository repository = factory.getRepository(params);
> // ...
> {code}
> It seems like that {{Session#importXML(...)}} call invokes an AclResource
> Webdav request first on the specific resource path, but
> {{org.apache.jackrabbit.webdav.jcr.version.report.JcrPrivilegeReport#init(DavResource,
> ReportInfo)}} does not remove the contextPath, "/cms" for example, when
> determining the resoucrePath.
> Unlike the {{JcrPrivilegeReport}},
> {{org.apache.jackrabbit.webdav.WebdavRequestImpl#getHrefLocator(String,
> boolean)}} seems to remove the contextPath properly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4458) When JcrRemotingServlet deployed on non-root context, AclResource Webdav request fails
[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4458:
Attachment: JCR-4458.diff
> When JcrRemotingServlet deployed on non-root context, AclResource Webdav
> request fails
> --
>
> Key: JCR-4458
> URL: https://issues.apache.org/jira/browse/JCR-4458
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.18.2
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: JCR-4458.diff
>
>
> If {{org.apache.jackrabbit.server.remoting.davex.JcrRemotingServlet}} is
> configured in a non-root web application, the contextPath of which is "/cms"
> for example with the servletPath, "/server", then
> {{javax.jcr.Session#importXML(...)}} fails from a JCR client based on
> JCR/WebDAV. In other words, {{#importXML(...)}} fails from a JCR {{Session}}
> using a repository which can be created like the following for JCR over
> WebDAV:
> {code}
> String repositoryAddress = "http://localhost:8080/cms/server;;
> Jcr2davRepositoryFactory factory = new Jcr2davRepositoryFactory();
> Map params = new HashMap();
> params.put(JcrUtils.REPOSITORY_URI, repositoryAddress);
> Repository repository = factory.getRepository(params);
> // ...
> {code}
> It seems like that {{Session#importXML(...)}} call invokes an AclResource
> Webdav request first on the specific resource path, but
> {{org.apache.jackrabbit.webdav.jcr.version.report.JcrPrivilegeReport#init(DavResource,
> ReportInfo)}} does not remove the contextPath, "/cms" for example, when
> determining the resoucrePath.
> Unlike the {{JcrPrivilegeReport}},
> {{org.apache.jackrabbit.webdav.WebdavRequestImpl#getHrefLocator(String,
> boolean)}} seems to remove the contextPath properly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JCR-4458) When JcrRemotingServlet deployed on non-root context, AclResource Webdav request fails
[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918621#comment-16918621
]
Julian Reschke commented on JCR-4458:
-
[~woon_san] - so the changes in
{{jackrabbit-jcr2dav/src/test/java/org/apache/jackrabbit/jcr2dav/RepositoryStubImpl.java}}
allow us to testa setup that we did not test before, and which will fail
without the other changes, right?
In that case I'd like to split that into a separate issue, and get it into the
code base right now.
WRT the actual change: I understand you ruled out changing/extending APIs in a
way that would avoid the thread local?
> When JcrRemotingServlet deployed on non-root context, AclResource Webdav
> request fails
> --
>
> Key: JCR-4458
> URL: https://issues.apache.org/jira/browse/JCR-4458
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.18.2
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: JCR-4458.diff
>
>
> If {{org.apache.jackrabbit.server.remoting.davex.JcrRemotingServlet}} is
> configured in a non-root web application, the contextPath of which is "/cms"
> for example with the servletPath, "/server", then
> {{javax.jcr.Session#importXML(...)}} fails from a JCR client based on
> JCR/WebDAV. In other words, {{#importXML(...)}} fails from a JCR {{Session}}
> using a repository which can be created like the following for JCR over
> WebDAV:
> {code}
> String repositoryAddress = "http://localhost:8080/cms/server;;
> Jcr2davRepositoryFactory factory = new Jcr2davRepositoryFactory();
> Map params = new HashMap();
> params.put(JcrUtils.REPOSITORY_URI, repositoryAddress);
> Repository repository = factory.getRepository(params);
> // ...
> {code}
> It seems like that {{Session#importXML(...)}} call invokes an AclResource
> Webdav request first on the specific resource path, but
> {{org.apache.jackrabbit.webdav.jcr.version.report.JcrPrivilegeReport#init(DavResource,
> ReportInfo)}} does not remove the contextPath, "/cms" for example, when
> determining the resoucrePath.
> Unlike the {{JcrPrivilegeReport}},
> {{org.apache.jackrabbit.webdav.WebdavRequestImpl#getHrefLocator(String,
> boolean)}} seems to remove the contextPath properly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843959#comment-16843959 ] Julian Reschke edited comment on JCR-4438 at 8/29/19 2:08 PM: -- trunk: (2.19.4) [r1859563|http://svn.apache.org/r1859563] 2.18: (2.18.3) [r1863251|http://svn.apache.org/r1863251] 2.16: [r1866075|http://svn.apache.org/r1866075] was (Author: reschke): trunk: [r1859563|http://svn.apache.org/r1859563] > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4438: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4438: Fix Version/s: 2.16.5 > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4437) Update Tika dependency to 1.21
[ https://issues.apache.org/jira/browse/JCR-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4437: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > Update Tika dependency to 1.21 > -- > > Key: JCR-4437 > URL: https://issues.apache.org/jira/browse/JCR-4437 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4437) Update Tika dependency to 1.21
[ https://issues.apache.org/jira/browse/JCR-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4437: Fix Version/s: 2.16.5 > Update Tika dependency to 1.21 > -- > > Key: JCR-4437 > URL: https://issues.apache.org/jira/browse/JCR-4437 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCR-4458) When JcrRemotingServlet deployed on non-root context, AclResource Webdav request fails
[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918656#comment-16918656
]
Woonsan Ko commented on JCR-4458:
-
Hi [~reschke],
Yes, the changes fix the test case #4 in my last comment in JCR-4460: "With
custom context path". And the other changes in RepositoryStubImpl are
improvements to allow servlet path configurations as well.
And the reason why I ruled out the option of "changing/extending APIs in a way
that would avoid the thread local" is that I thought another approach I took in
https://github.com/apache/jackrabbit/pull/84 is hard to understand in
maintenance perspective and is by itself kind of indirect inference of context
path anyway. So, I thought it seems better to directly access and use the
request to determine the context path and easier to maintain..
Regards,
Woonsan
> When JcrRemotingServlet deployed on non-root context, AclResource Webdav
> request fails
> --
>
> Key: JCR-4458
> URL: https://issues.apache.org/jira/browse/JCR-4458
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.18.2
>Reporter: Woonsan Ko
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.20
>
> Attachments: JCR-4458.diff
>
>
> If {{org.apache.jackrabbit.server.remoting.davex.JcrRemotingServlet}} is
> configured in a non-root web application, the contextPath of which is "/cms"
> for example with the servletPath, "/server", then
> {{javax.jcr.Session#importXML(...)}} fails from a JCR client based on
> JCR/WebDAV. In other words, {{#importXML(...)}} fails from a JCR {{Session}}
> using a repository which can be created like the following for JCR over
> WebDAV:
> {code}
> String repositoryAddress = "http://localhost:8080/cms/server;;
> Jcr2davRepositoryFactory factory = new Jcr2davRepositoryFactory();
> Map params = new HashMap();
> params.put(JcrUtils.REPOSITORY_URI, repositoryAddress);
> Repository repository = factory.getRepository(params);
> // ...
> {code}
> It seems like that {{Session#importXML(...)}} call invokes an AclResource
> Webdav request first on the specific resource path, but
> {{org.apache.jackrabbit.webdav.jcr.version.report.JcrPrivilegeReport#init(DavResource,
> ReportInfo)}} does not remove the contextPath, "/cms" for example, when
> determining the resoucrePath.
> Unlike the {{JcrPrivilegeReport}},
> {{org.apache.jackrabbit.webdav.WebdavRequestImpl#getHrefLocator(String,
> boolean)}} seems to remove the contextPath properly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4442) Update animal-sniffer dependency to 1.18
[ https://issues.apache.org/jira/browse/JCR-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4442: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > Update animal-sniffer dependency to 1.18 > > > Key: JCR-4442 > URL: https://issues.apache.org/jira/browse/JCR-4442 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4442) Update animal-sniffer dependency to 1.18
[ https://issues.apache.org/jira/browse/JCR-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4442: Fix Version/s: 2.16.5 > Update animal-sniffer dependency to 1.18 > > > Key: JCR-4442 > URL: https://issues.apache.org/jira/browse/JCR-4442 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4447: Fix Version/s: 2.16.5 > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4441: Labels: candidate_jcr_2_14 (was: ) > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4441: Labels: (was: candidate_jcr_2_16) > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4441: Fix Version/s: 2.16.5 > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856416#comment-16856416 ] Julian Reschke edited comment on JCR-4447 at 8/29/19 3:07 PM: -- trunk: (2.19.4) [r1860645|http://svn.apache.org/r1860645] 2.18: (2.18.3) [r1863254|http://svn.apache.org/r1863254] 2.16: [r1866079|http://svn.apache.org/r1866079] was (Author: reschke): trunk: [r1860645|http://svn.apache.org/r1860645] 2.18: [r1863254|http://svn.apache.org/r1863254] > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4447: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869397#comment-16869397 ] Julian Reschke edited comment on JCR-4450 at 8/29/19 5:13 PM: -- trunk: (2.19.4) [r1861773|http://svn.apache.org/r1861773] 2.18: (2.18.3) [r1863255|http://svn.apache.org/r1863255] 2.16: [r1866090|http://svn.apache.org/r1866090] was (Author: reschke): trunk: [r1861773|http://svn.apache.org/r1861773] 2.18: [r1863255|http://svn.apache.org/r1863255] > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4450: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4450: Fix Version/s: 2.16.5 > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-358) XmlAnalyser.analyze does not correctly detect regular (non FileVault) DocView xml
[
https://issues.apache.org/jira/browse/JCRVLT-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919041#comment-16919041
]
Tobias Bocanegra commented on JCRVLT-358:
-
I think that we can explicitly not support regular docview (and sysview). I
don't think there is any benefit.
> XmlAnalyser.analyze does not correctly detect regular (non FileVault) DocView
> xml
> -
>
> Key: JCRVLT-358
> URL: https://issues.apache.org/jira/browse/JCRVLT-358
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Konrad Windszus
>Priority: Major
>
> Only doc view files starting with element {{jcr:root}} are detected due to
> https://github.com/apache/jackrabbit-filevault/blob/2cf781d74fa18d86d061f9962c51f7470cac4096/vault-sync/src/main/java/org/apache/jackrabbit/vault/sync/impl/XmlAnalyzer.java#L83.
> But regular docview allows arbitrary elements according to
> https://docs.adobe.com/docs/en/spec/jcr/2.0/7_Export.html#7.3%20Document%20View
> (in contrast to the extended doc view from FileVault:
> https://jackrabbit.apache.org/filevault/docview.html). For regular docview
> files always {{SerializationType.XML_GENERIC}} is being returned.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869418#comment-16869418 ] Julian Reschke edited comment on JCR-4452 at 8/29/19 6:14 PM: -- trunk: (2.19.4) [r1861778|http://svn.apache.org/r1861778] 2.18: (2.18.3) [r1863263|http://svn.apache.org/r1863263] 2.16: [r1866093|http://svn.apache.org/r1866093] was (Author: reschke): trunk: [r1861778|http://svn.apache.org/r1861778] 2.18: [r1863263|http://svn.apache.org/r1863263] > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869455#comment-16869455 ] Julian Reschke edited comment on JCR-4454 at 8/29/19 7:08 PM: -- trunk: (2.19.4) [r1861786|http://svn.apache.org/r1861786] 2.18: (2.18.3) [r1863269|http://svn.apache.org/r1863269] 2.16: [r1866100|http://svn.apache.org/r1866100] was (Author: reschke): trunk: [r1861786|http://svn.apache.org/r1861786] 2.18: [r1863269|http://svn.apache.org/r1863269] > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4451: Fix Version/s: 2.16.5 > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4451: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869405#comment-16869405 ] Julian Reschke edited comment on JCR-4451 at 8/29/19 5:49 PM: -- trunk: (2.19.4) [r1861777|http://svn.apache.org/r1861777] 2.18: (2.18.3) [r1863258|http://svn.apache.org/r1863258] 2.16: [r1866091|http://svn.apache.org/r1866091] was (Author: reschke): trunk: [r1861777|http://svn.apache.org/r1861777] 2.18: [r1863258|http://svn.apache.org/r1863258] > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915551#comment-16915551
]
Julian Reschke edited comment on JCR-4455 at 8/29/19 7:33 PM:
--
trunk: (2.19.4) [r1862805|http://svn.apache.org/r1862805]
[r1862783|http://svn.apache.org/r1862783]
2.18: (2.18.3) [r1865913|http://svn.apache.org/r1865913]
2.16: [r1866101|http://svn.apache.org/r1866101]
was (Author: reschke):
trunk: (2.19.4) [r1862805|http://svn.apache.org/r1862805]
[r1862783|http://svn.apache.org/r1862783]
2.18: [r1865913|http://svn.apache.org/r1865913]
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4455:
Fix Version/s: 2.16.5
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4455:
Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16)
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.19.4, 2.18.3
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4454: Fix Version/s: 2.16.5 > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4454: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874914#comment-16874914 ] Julian Reschke edited comment on JCR-4457 at 8/29/19 8:17 PM: -- trunk: (2.19.4) [r1862283|http://svn.apache.org/r1862283] 2.18: (2.18.3) [r1863270|http://svn.apache.org/r1863270] 2.16: [r1866104|http://svn.apache.org/r1866104] was (Author: reschke): trunk: [r1862283|http://svn.apache.org/r1862283] 2.18: [r1863270|http://svn.apache.org/r1863270] > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4457: Fix Version/s: 2.16.5 > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4457: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4452: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4452: Fix Version/s: 2.16.5 > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869440#comment-16869440 ] Julian Reschke edited comment on JCR-4453 at 8/29/19 6:46 PM: -- trunk: (2.19.4) [r1861781|http://svn.apache.org/r1861781] 2.18: (2.18.3) [r1863264|http://svn.apache.org/r1863264] 2.16: [r1866099|http://svn.apache.org/r1866099] was (Author: reschke): trunk: [r1861781|http://svn.apache.org/r1861781] 2.18: [r1863264|http://svn.apache.org/r1863264] > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4453: Fix Version/s: 2.16.5 > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4453: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-359) Provide separate option to control handling of rep:cugPolicy nodes.
[
https://issues.apache.org/jira/browse/JCRVLT-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919044#comment-16919044
]
Tobias Bocanegra commented on JCRVLT-359:
-
I do not really understand the problem. AFAIK, the {{rep:cugPolicy}} are a
special kind of policy nodes, thus are related to ACL handing. if their
serialization is missing or wrong, this needs to be added to the special ACL
handling. /cc [~angela]
> Provide separate option to control handling of rep:cugPolicy nodes.
> ---
>
> Key: JCRVLT-359
> URL: https://issues.apache.org/jira/browse/JCRVLT-359
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Affects Versions: 3.2.8
>Reporter: Alexei Krainiouk
>Priority: Major
>
> Currently handling of rep:cugPolicy nodes is controlled by aclHandling
> configuration option that equally affects ACLs and CUGs. We need to control
> them separately as for replication that is based on sling-distribution we
> need to ignore ACLs while overwriting CUGs
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4459: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4459: Fix Version/s: 2.16.5 > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886880#comment-16886880 ] Julian Reschke edited comment on JCR-4459 at 8/30/19 4:11 AM: -- trunk: (2.19.4) [r1863196|http://svn.apache.org/r1863196] 2.18: (2.18.3) [r1863249|http://svn.apache.org/r1863249] 2.16: [r1866111|http://svn.apache.org/r1866111] was (Author: reschke): trunk: (2.19.4) [r1863196|http://svn.apache.org/r1863196] 2.18: [r1863249|http://svn.apache.org/r1863249] > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4460:
Fix Version/s: 2.16.5
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_16
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919177#comment-16919177
]
Julian Reschke edited comment on JCR-4460 at 8/30/19 4:50 AM:
--
trunk: (2.19.4) [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: (2.18.3) [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
2.16: [r1866114|http://svn.apache.org/r1866114]
was (Author: reschke):
trunk: (2.19.4) [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: (2.18.3) [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4460:
Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16)
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Issue Comment Deleted] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4460:
Comment: was deleted
(was: trunk: [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
)
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_16
> Fix For: 2.20, 2.19.4, 2.18.3
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919177#comment-16919177
]
Julian Reschke commented on JCR-4460:
-
trunk: (2.19.4) [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: (2.18.3) [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_16
> Fix For: 2.20, 2.19.4, 2.18.3
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
