[beam-site] 03/08: Drop using gradle clean in favor of --rerun-tasks

[me...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit 0d4a0cee327a6a48fac37d3139e7b0ce723fad16
Author: Lukasz Cwik <lc...@google.com>
AuthorDate: Mon Apr 9 12:52:04 2018 -0400

    Drop using gradle clean in favor of --rerun-tasks
---
 src/contribute/contribution-guide.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/contribute/contribution-guide.md b/src/contribute/contribution-guide.md
index 9d9d38e..4b60154 100644
--- a/src/contribute/contribution-guide.md
+++ b/src/contribute/contribution-guide.md
@@ -248,7 +248,7 @@ to prevent the issue from reoccurring.
 
 For contributions to the Java code, run checks locally via Gradle.
 
-    $ ./gradlew clean && ./gradlew :beam-sdks-java-core:check
+    $ ./gradlew :beam-sdks-java-core:check --rerun-tasks
 
 #### Python SDK
 
@@ -275,7 +275,7 @@ Beam supports running Python SDK tests using Gradle. For this, navigate to root
 directory of your Apache Beam clone and execute following command. Currently
 this cannot be run from a virtual environment.
 
-    $ ./gradlew clean && ./gradlew :beam-sdks-python:check
+    $ ./gradlew :beam-sdks-python:check --rerun-tasks
 
 ## Review
 

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.