Re: New Jackrabbit Committer: Dominik Süß
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 with Jackrabbit in 2007 and became an active member mostly of the Sling Community soon after. In 2015 I joined AEM engineering and by that rather worked more on the details of the stack and began to contribute once in a while. Since a few years my focus is mostly around deployment aspects as content that links directly to application that may change over time or the installation and necessary transformation of content over time without having negative impact on the availability of a system. I share Konrads interest in filevault but also correlated topics such as composite node-store, oak-upgrade and any other mechanism that link to automation of changes in Jackrabbit. Cheers Dominik On Thu, Jul 25, 2019 at 4:02 PM Woonsan Ko wrote: > Welcome, Dominik! > > Cheers, > > Woonsan > > On Thu, Jul 25, 2019 at 9:54 AM Marcel Reutegger > wrote: > > > > Hi, > > > > Please welcome Dominik Süß as a new committer and PMC member of > > the Apache Jackrabbit project. The Jackrabbit PMC recently decided to > > offer Dominik committership based on his contributions. I'm happy to > > announce that he accepted the offer and that all the related > > administrative work has now been taken care of. > > > > Welcome to the team, Dominik! > > > > Regards > > Marcel >
Re: New Jackrabbit Committer: Dominik Süß
Welcome, Dominik! Cheers, Woonsan On Thu, Jul 25, 2019 at 9:54 AM Marcel Reutegger wrote: > > Hi, > > Please welcome Dominik Süß as a new committer and PMC member of > the Apache Jackrabbit project. The Jackrabbit PMC recently decided to > offer Dominik committership based on his contributions. I'm happy to > announce that he accepted the offer and that all the related > administrative work has now been taken care of. > > Welcome to the team, Dominik! > > Regards > Marcel
Re: New Jackrabbit Committer: Konrad Windszus
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 with AEM/CQ since 2005. I am now > working for Netcentric. I joined the Apache family in 2014 by becoming an > Apache Sling committer. Meanwhile I am part of the Apache Sling PMC. > > I am looking forward to contribute even more in the future to Jackrabbit/Oak. > Particularly I am interested in improving Filevault and the related Maven > Plugin. > > Konrad > > > > On 24. Jul 2019, at 15:37, Marcel Reutegger wrote: > > > > Hi, > > > > Please welcome Konrad Windszus as a new committer and PMC member of > > the Apache Jackrabbit project. The Jackrabbit PMC recently decided to > > offer Konrad committership based on his contributions. I'm happy to > > announce that he accepted the offer and that all the related > > administrative work has now been taken care of. > > > > Welcome to the team, Konrad! > > > > Regards > > Marcel > > >
New Jackrabbit Committer: Dominik Süß
Hi, Please welcome Dominik Süß as a new committer and PMC member of the Apache Jackrabbit project. The Jackrabbit PMC recently decided to offer Dominik committership based on his contributions. I'm happy to announce that he accepted the offer and that all the related administrative work has now been taken care of. Welcome to the team, Dominik! Regards Marcel
[jira] [Commented] (JCRVLT-344) update version of jackrabbit and oak dependencies
[ https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892732#comment-16892732 ] Konrad Windszus commented on JCRVLT-344: [~angela] There is a typo in line 135 of the patch, apart from that LGTM. > update version of jackrabbit and oak dependencies > -- > > Key: JCRVLT-344 > URL: https://issues.apache.org/jira/browse/JCRVLT-344 > Project: Jackrabbit FileVault > Issue Type: Task > Components: Misc >Reporter: angela >Priority: Major > Attachments: JCRVLT-344.patch > > > in order to address JCRVLT-340 the version properties of jackrabbit and oak > need to be adjusted to use the most recent releases: > 2.18.2 > 1.16.0 > since there some significant moves made in the code base the following > additional changes need to follow: > * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer > exist) > - subsequently adjust the changed package names > (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) > - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as > jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (JCRVLT-344) update version of jackrabbit and oak dependencies
[ https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892720#comment-16892720 ] Julian Reschke commented on JCRVLT-344: --- I do not plan to remove jackrabbit-api in 2.18, so I would argue that using the old artefact name is ok as long as Jackrabbit 2.18.* is used. (It *will* go away in Jackrabbit 2.20). > update version of jackrabbit and oak dependencies > -- > > Key: JCRVLT-344 > URL: https://issues.apache.org/jira/browse/JCRVLT-344 > Project: Jackrabbit FileVault > Issue Type: Task > Components: Misc >Reporter: angela >Priority: Major > Attachments: JCRVLT-344.patch > > > in order to address JCRVLT-340 the version properties of jackrabbit and oak > need to be adjusted to use the most recent releases: > 2.18.2 > 1.16.0 > since there some significant moves made in the code base the following > additional changes need to follow: > * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer > exist) > - subsequently adjust the changed package names > (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) > - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as > jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[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&focusedCommentId=16892655#comment-16892655
]
Woonsan Ko commented on JCR-4460:
-
One theoretical use case of the explicit path prefix init param is when the
servlet doesn’t have a servlet path. For example, a filter uses a named
dispatcher to the servlet.
> 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: 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
(v7.6.14#76016)
[jira] [Created] (JCRVLT-345) Support pluggable node/file/filter validators
Konrad Windszus created JCRVLT-345:
--
Summary: Support pluggable node/file/filter validators
Key: JCRVLT-345
URL: https://issues.apache.org/jira/browse/JCRVLT-345
Project: Jackrabbit FileVault
Issue Type: New Feature
Components: package maven plugin
Reporter: Konrad Windszus
IMHO it would be good to support pluggable node, file and filter.xml validators
for custom validations:
The filevault-package-m-p should ship/ships with these ones out of the box
# check for index definition nodes
# check for bundles, OSGi configuration and subpackages (in the context of
JCRVLT-249)
# check for adherence to the FileVault DocView for .content.xml files
# check for filter.xml coverage of all nodes/files
The following ones are just ideas for custom validations:
# check for usage of deprecated resource types
# check for content classification
(https://helpx.adobe.com/experience-manager/6-5/sites/deploying/using/sustainable-upgrades.html)
An SPI should be defined and allow everyone to come up with validator
extensions which are automatically executed during the {{package}} goal on all
files/nodes being included in the package
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (JCRVLT-232) Enforce constraints for package types
[
https://issues.apache.org/jira/browse/JCRVLT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892610#comment-16892610
]
Konrad Windszus commented on JCRVLT-232:
Removing OSGi bundles and configuration should also be forbidden in
{{application}} and {{content}} packages. In that case this must rather be a
best guess, as one cannot be sure at build time, if a filter root like
{{/apps/myapp/install}} will actually remove a bundle/config at installation
time...
[~tripod] Any idea on how to check this properly as the JCR Installer in Sling
(IMHO the only feature which deploys OSGi bundles/configuration from a
repository into the OSGi container) can be freely configured to only consider
certain node names (configuration might differ from server to server) and even
supports run mode specific deployments
(https://sling.apache.org/documentation/bundles/jcr-installer-provider.html).
> Enforce constraints for package types
> -
>
> Key: JCRVLT-232
> URL: https://issues.apache.org/jira/browse/JCRVLT-232
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently the package type only affects how the dependencies are considered
> to check for invalid filter rules (and only for package type "application").
> This contradicts the javadoc of the parameter which states that
> {quote}'application' and 'content' packages are not allowed to contain sub
> packages or embedded bundles.{quote}
> (https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/02a853e64d985f075fe88d19101d7c66d741767f/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/AbstractPackageMojo.java#L104)
> As long as this is not enforced during package build time please only list
> the enforced limitations of the according package types.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (JCRVLT-343) Check for index definitions also considers ACL entries
[
https://issues.apache.org/jira/browse/JCRVLT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892606#comment-16892606
]
Konrad Windszus commented on JCRVLT-343:
[~tripod] I think it is also questionable if just embedding a subpackage
containing an index definition should require the container package to set
`allowIndexDefinitions=true` as well. WDYT?
> Check for index definitions also considers ACL entries
> --
>
> Key: JCRVLT-343
> URL: https://issues.apache.org/jira/browse/JCRVLT-343
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: package-maven-plugin-1.0.5
>
>
> The package for acs-aem-commons contains a rep:policy node at
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jcr_root/_oak_index/_rep_policy.xml.
> This leads to the following build error when embedding
> acs-aem-commons-content in your own package as subpackage.
> {code}
>
> [INFO] --- filevault-package-maven-plugin:1.0.4:package (default-package) @
> ... ---
> [INFO] using meta-inf/vault from
> /Users/konradwindszus/git/.../src/main/META-INF/vault
> [INFO] Scanning files for oak index definitions.
> [ERROR] Package contains index /oak:index/rep:policy in filter, but not in
> package. Existing index will be removed.
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 14.793 s
> [INFO] Finished at: 2019-07-25T11:25:51+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project ...:
> org.apache.maven.plugin.MojoExecutionException: Package should not contain
> index definitions, because 'allowIndexDefinitions=false'. -> [Help 1]
> [ERROR]
> .
> {code}
> Either the check should be relaxed to skip rep:policy nodes or the warning
> message should be adjusted.
> The issue was originally reported through
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1988.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (JCRVLT-232) Enforce constraints for package types
[
https://issues.apache.org/jira/browse/JCRVLT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned JCRVLT-232:
--
Assignee: Konrad Windszus
> Enforce constraints for package types
> -
>
> Key: JCRVLT-232
> URL: https://issues.apache.org/jira/browse/JCRVLT-232
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently the package type only affects how the dependencies are considered
> to check for invalid filter rules (and only for package type "application").
> This contradicts the javadoc of the parameter which states that
> {quote}'application' and 'content' packages are not allowed to contain sub
> packages or embedded bundles.{quote}
> (https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/02a853e64d985f075fe88d19101d7c66d741767f/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/AbstractPackageMojo.java#L104)
> As long as this is not enforced during package build time please only list
> the enforced limitations of the according package types.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (JCRVLT-344) update version of jackrabbit and oak dependencies
[ https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892588#comment-16892588 ] angela commented on JCRVLT-344: --- [~tripod], proposed patch attached. i tested it with the release-candidate of oak 1.16.0. once oak 1.16.0 is released, the patch could be committed. let me know if you have any concerns. > update version of jackrabbit and oak dependencies > -- > > Key: JCRVLT-344 > URL: https://issues.apache.org/jira/browse/JCRVLT-344 > Project: Jackrabbit FileVault > Issue Type: Task > Components: Misc >Reporter: angela >Priority: Major > Attachments: JCRVLT-344.patch > > > in order to address JCRVLT-340 the version properties of jackrabbit and oak > need to be adjusted to use the most recent releases: > 2.18.2 > 1.16.0 > since there some significant moves made in the code base the following > additional changes need to follow: > * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer > exist) > - subsequently adjust the changed package names > (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) > - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as > jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (JCRVLT-343) Check for index definitions also considers ACL entries
[
https://issues.apache.org/jira/browse/JCRVLT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-343:
---
Description:
The package for acs-aem-commons contains a rep:policy node at
https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jcr_root/_oak_index/_rep_policy.xml.
This leads to the following build error when embedding acs-aem-commons-content
in your own package as subpackage.
{code}
[INFO] --- filevault-package-maven-plugin:1.0.4:package (default-package) @ ...
---
[INFO] using meta-inf/vault from
/Users/konradwindszus/git/.../src/main/META-INF/vault
[INFO] Scanning files for oak index definitions.
[ERROR] Package contains index /oak:index/rep:policy in filter, but not in
package. Existing index will be removed.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 14.793 s
[INFO] Finished at: 2019-07-25T11:25:51+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
(default-package) on project ...:
org.apache.maven.plugin.MojoExecutionException: Package should not contain
index definitions, because 'allowIndexDefinitions=false'. -> [Help 1]
[ERROR]
.
{code}
Either the check should be relaxed to skip rep:policy nodes or the warning
message should be adjusted.
The issue was originally reported through
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1988.
was:
The package for acs-aem-commons contains a rep:policy node at
https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jcr_root/_oak_index/_rep_policy.xml.
This leads to the exception {{Package should not contain index definitions,
because 'allowIndexDefinitions=false'.}}
Either the check should be relaxed to skip rep:policy nodes or the warning
message should be adjusted.
The issue was originally reported through
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1988.
> Check for index definitions also considers ACL entries
> --
>
> Key: JCRVLT-343
> URL: https://issues.apache.org/jira/browse/JCRVLT-343
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: package-maven-plugin-1.0.5
>
>
> The package for acs-aem-commons contains a rep:policy node at
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jcr_root/_oak_index/_rep_policy.xml.
> This leads to the following build error when embedding
> acs-aem-commons-content in your own package as subpackage.
> {code}
>
> [INFO] --- filevault-package-maven-plugin:1.0.4:package (default-package) @
> ... ---
> [INFO] using meta-inf/vault from
> /Users/konradwindszus/git/.../src/main/META-INF/vault
> [INFO] Scanning files for oak index definitions.
> [ERROR] Package contains index /oak:index/rep:policy in filter, but not in
> package. Existing index will be removed.
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 14.793 s
> [INFO] Finished at: 2019-07-25T11:25:51+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project ...:
> org.apache.maven.plugin.MojoExecutionException: Package should not contain
> index definitions, because 'allowIndexDefinitions=false'. -> [Help 1]
> [ERROR]
> .
> {code}
> Either the check should be relaxed to skip rep:policy nodes or the warning
> message should be adjusted.
> The issue was originally reported through
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1988.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (JCRVLT-344) update version of jackrabbit and oak dependencies
[ https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCRVLT-344: -- Attachment: JCRVLT-344.patch > update version of jackrabbit and oak dependencies > -- > > Key: JCRVLT-344 > URL: https://issues.apache.org/jira/browse/JCRVLT-344 > Project: Jackrabbit FileVault > Issue Type: Task > Components: Misc >Reporter: angela >Priority: Major > Attachments: JCRVLT-344.patch > > > in order to address JCRVLT-340 the version properties of jackrabbit and oak > need to be adjusted to use the most recent releases: > 2.18.2 > 1.16.0 > since there some significant moves made in the code base the following > additional changes need to follow: > * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer > exist) > - subsequently adjust the changed package names > (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) > - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as > jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[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&focusedCommentId=16892577#comment-16892577
]
Felix Meschberger commented on JCR-4460:
You might want to look how it is being used in the Sling JCR WebDAV bundles for
some more insight, [~reschke]
> 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: 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
(v7.6.14#76016)
[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&focusedCommentId=16892552#comment-16892552
]
Julian Reschke commented on JCR-4460:
-
[~fmeschbe], [~woon_san], thanks for the feedback.
My preference would be to
1) understand and document the role of the init parameter
2) see how it can be used to make jackrabbit-boot (and also the jackrabbit
webapp) do the right thing
and then
3) see whether we can make things work in absence of the init parameter as well
(see [^use-context-path.diff]) without breaking existing usages in OSGi
frameworks.
> 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: 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
(v7.6.14#76016)
[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&focusedCommentId=16892531#comment-16892531
]
Felix Meschberger commented on JCR-4460:
{quote}There probably was a good reason for it's introduction
{quote}
I guess so, yes. But I cannot remember. One explanation I would have is usage
inside an OSGi framework where the servlet context path might be injected
differently... But honestly, I do not remember ...
> 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: 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
(v7.6.14#76016)
[jira] [Created] (JCRVLT-344) update version of jackrabbit and oak dependencies
angela created JCRVLT-344: - Summary: update version of jackrabbit and oak dependencies Key: JCRVLT-344 URL: https://issues.apache.org/jira/browse/JCRVLT-344 Project: Jackrabbit FileVault Issue Type: Task Components: Misc Reporter: angela in order to address JCRVLT-340 the version properties of jackrabbit and oak need to be adjusted to use the most recent releases: 2.18.2 1.16 since there some significant moves made in the code base the following additional changes need to follow: * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer exist) - subsequently adjust the changed package names (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (JCRVLT-344) update version of jackrabbit and oak dependencies
[ https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCRVLT-344: -- Description: in order to address JCRVLT-340 the version properties of jackrabbit and oak need to be adjusted to use the most recent releases: 2.18.2 1.16.0 since there some significant moves made in the code base the following additional changes need to follow: * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer exist) - subsequently adjust the changed package names (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as jackrabbit-api will no longer be maintained was: in order to address JCRVLT-340 the version properties of jackrabbit and oak need to be adjusted to use the most recent releases: 2.18.2 1.16 since there some significant moves made in the code base the following additional changes need to follow: * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer exist) - subsequently adjust the changed package names (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as jackrabbit-api will no longer be maintained > update version of jackrabbit and oak dependencies > -- > > Key: JCRVLT-344 > URL: https://issues.apache.org/jira/browse/JCRVLT-344 > Project: Jackrabbit FileVault > Issue Type: Task > Components: Misc >Reporter: angela >Priority: Major > > in order to address JCRVLT-340 the version properties of jackrabbit and oak > need to be adjusted to use the most recent releases: > 2.18.2 > 1.16.0 > since there some significant moves made in the code base the following > additional changes need to follow: > * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer > exist) > - subsequently adjust the changed package names > (o.a.jackrabbit.oak.plugins.segment to o.a.jackrabbit.segment) > - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as > jackrabbit-api will no longer be maintained -- This message was sent by Atlassian JIRA (v7.6.14#76016)
