You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by st...@apache.org on 2016/03/01 13:54:26 UTC
svn commit: r1733060 -
/jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md
Author: stefanegli
Date: Tue Mar 1 12:54:25 2016
New Revision: 1733060
URL: http://svn.apache.org/viewvc?rev=1733060&view=rev
Log:
OAK-4062 : applying docu patch from Tomek re --include-paths parameter
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md?rev=1733060&r1=1733059&r2=1733060&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/migration.md Tue Mar 1 12:54:25 2016
@@ -144,10 +144,13 @@ You may also exclude specific paths from
By default, the source repository replaces the destination repository (if there's one). For instance, in the first example if the `/content/site` node already exists in the destination repository, it'll be removed and replaced by the source node. It's also possible to merge content from the source repository with `--merge-paths`:
java -jar oak-upgrade-*.jar \
+ --include-paths=/content/site \
--merge-paths=/content/site \
/old/repository \
/new/repository
+Please notice that in the last example it's necessary to narrow the migration scope using `--include-paths` parameter.
+
### Version history copying
