You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/03/01 13:56:18 UTC

[jira] [Resolved] (OAK-4062) Update the merge-paths example in the migration doc

     [ https://issues.apache.org/jira/browse/OAK-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli resolved OAK-4062.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.4.0

Applied patch from [~tomek.rekawek] in http://svn.apache.org/viewvc?rev=1733060&view=rev - thx!

> Update the merge-paths example in the migration doc
> ---------------------------------------------------
>
>                 Key: OAK-4062
>                 URL: https://issues.apache.org/jira/browse/OAK-4062
>             Project: Jackrabbit Oak
>          Issue Type: Documentation
>          Components: doc, upgrade
>            Reporter: Tomek Rękawek
>            Assignee: Stefan Egli
>             Fix For: 1.4.0
>
>         Attachments: OAK-4062.patch
>
>
> In order to merge only a specific path, like {{/content/mypath}} (it already exists), both {{\-\-include\-paths=/content/mypath}} *and* {{\-\-merge\-paths=/content/mypath}} should be passed.
> Without {{\-\-include-paths}}, the resulting paths will be as follows:
> {noformat}
> i: [/etc, /rep:repoPolicy, /content, /rep:policy, /libs, /apps, /jcr:system, /home, /bin, /var, /tmp]
> e: [/jcr:system/jcr:versionStorage], 
> m : [/content mypath]
> {noformat}
> Please update the merge-paths example in the migration documentation accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)