[
https://issues.apache.org/jira/browse/JCR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16894062#comment-16894062
]
Woonsan Ko commented on JCR-4458:
-
I thought it would be straightforward by prepending the contextPath to
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16894059#comment-16894059
]
Woonsan Ko commented on JCR-4460:
-
Hi [~reschke],
I've attached a new patch only for this ticket:
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-4460:
Attachment: servlet_path_prefix.patch
> allow to run remoted conformance tests with a custom servlet context
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893973#comment-16893973
]
Woonsan Ko commented on JCR-4460:
-
Now I realize that the {{INIT_PARAM_RESOURCE_PATH_PREFIX}} init
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893921#comment-16893921
]
Woonsan Ko commented on JCR-4460:
-
Hi [~reschke],
I will try, but shouldn't it concatenate the contextPath
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893809#comment-16893809
]
Julian Reschke commented on JCR-4460:
-
[~fmeschbe] - I looked at
Welcome, Dominik!
Regards
Julian
On Thu, Jul 25, 2019 at 5:17 PM Dominik Süß wrote:
>
> Hello everyone,
>
> Like Konrad I wanted to thank a lot for the invitation.
>
>
> Here a short version about my own background. I started working as Integrator
> for AEM/CQ and that way getting in touch
Welcome Konrad!
Regards
Julian
On Thu, Jul 25, 2019 at 4:02 PM Woonsan Ko wrote:
>
> Welcome, Konrad!
>
> Cheers,
>
> Woonsan
>
> On Wed, Jul 24, 2019 at 10:11 AM Konrad Windszus wrote:
> >
> > Hi everyone,
> > thanks a lot for having invited me.
> > Some words about myself: I have experience
[
https://issues.apache.org/jira/browse/JCR-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4449:
Summary: remove jackrabbit-api and use oak-jackrabbit-api instead (was:
remove jackrabbit-api
[
https://issues.apache.org/jira/browse/JCR-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4449:
Description:
The subproject "jackrabbit-api" has been moved to Oak as per OAK-8339. After
the next
[
https://issues.apache.org/jira/browse/JCR-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4449:
Fix Version/s: 2.20
> remove jackrabbit-api project once Oak 1.16.0 is released
>
[
https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893479#comment-16893479
]
Julian Reschke commented on JCRVLT-344:
---
[~angela] - I see.
> update version of jackrabbit and oak
angela created JCRVLT-346:
-
Summary: IntegrationTestBase: allow for custom security setup
Key: JCRVLT-346
URL: https://issues.apache.org/jira/browse/JCRVLT-346
Project: Jackrabbit FileVault
Issue
[
https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893476#comment-16893476
]
angela commented on JCRVLT-344:
---
[~kwin], good catch. fixed in my local changes.
> update version of
[
https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCRVLT-344:
-
Assignee: angela
> update version of jackrabbit and oak dependencies
>
[
https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893453#comment-16893453
]
angela commented on JCRVLT-344:
---
[~reschke], the reason why i decided to move to _oak-jackrabbit-api_ was
[
https://issues.apache.org/jira/browse/JCRVLT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893432#comment-16893432
]
Jörg Hoh commented on JCRVLT-345:
-
This function is crucial to the build process, I agree. But I don't
[
https://issues.apache.org/jira/browse/JCRVLT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893417#comment-16893417
]
Konrad Windszus commented on JCRVLT-345:
I don't think it is an issue to put the validations in a
Thanks for the input.
Although this is easy to determine for new/modified index definitions, this is
impossible to tell for paths below /oak:index which are just getting removed
(i.e. are just listed in the filter). I guess for the latter we have to assume
the worst, case i.e. that an existing
Hi Konrad,
As written in JCRVLT-345, I don't think that we should add a lot of
validation features into the filevault-package-m-p, as validation can
happen more often during the lifetime of a package (e.g. before deployment
if developer and deployer/operation are not identical). I would move all
[
https://issues.apache.org/jira/browse/JCRVLT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893407#comment-16893407
]
Jörg Hoh commented on JCRVLT-345:
-
If we build this into the filevault-package-m-p, these checks can be
21 matches
Mail list logo
