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 d9634716be5d28a898ebc5e5be506b6c16a85d5f
Author: Boyuan Zhang <boyu...@google.com>
AuthorDate: Thu Jun 7 11:22:06 2018 -0700
Update gradle publish with --no-parallel --no-daemon
---
src/contribute/release-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 4c9c536..b2abf32 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -337,7 +337,7 @@ release tag to the origin repository (this would be the
Apache Beam repo):
Use Gradle publish plugin to stage these artifacts on the Apache Nexus
repository, as follows:
- ./gradlew publish -PisRelease
+ ./gradlew publish -PisRelease --no-parallel --no-daemon
Review all staged artifacts. They should contain all relevant parts for each
module, including `pom.xml`, jar, test jar, javadoc, etc. Artifact names should
follow [the existing
format](https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22)
in which artifact name mirrors directory structure, e.g.,
`beam-sdks-java-io-kafka`. Carefully review any new artifacts.
--
To stop receiving notification emails like this one, please contact
mergebot-r...@apache.org.
