Repository: tinkerpop
Updated Branches:
  refs/heads/master d75940aae -> 5e271eaf3


Simplified command to "quick" generate recipes CTR


Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/d223d65e
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/d223d65e
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/d223d65e

Branch: refs/heads/master
Commit: d223d65ea27b3a274b5c75e4f4e8f7be240fad16
Parents: 0bffe25
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Fri Sep 29 12:44:29 2017 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Fri Sep 29 12:44:29 2017 -0400

----------------------------------------------------------------------
 docs/src/recipes/index.asciidoc | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/d223d65e/docs/src/recipes/index.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/recipes/index.asciidoc b/docs/src/recipes/index.asciidoc
index b98779f..f549b1f 100644
--- a/docs/src/recipes/index.asciidoc
+++ b/docs/src/recipes/index.asciidoc
@@ -110,14 +110,7 @@ run of the documentation as it is generating all of the 
documentation locally (e
 tutorials, etc). To generate just the recipes, follow this process:
 
 [source,shell]
-bin/process-docs.sh --dryRun               <1>
-rm -r target/postprocess-asciidoc/recipes  <2>
-bin/process-docs.sh                        <3>
-
-<1> That command will quickly generate all of the documentation, but it does 
not do the code example execution (which is
-the "slow" part).
-<2> Delete the recipes directory, which forces a fresh copy of the recipes to 
be generated.
-<3> Process all of the documentation that is "new" (i.e. the fresh copy of 
recipes).
+bin/process-docs.sh -f docs/src/recipes
 
 The `bin/process-docs.sh` approach requires that Hadoop is installed. To avoid 
that prerequisite, try using Docker:
 

Reply via email to