bullet03 commented on a change in pull request #17089:
URL: https://github.com/apache/beam/pull/17089#discussion_r833173568
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -160,102 +216,91 @@ script which is part of the Beam repo:
./start-build-env.sh
```
-### Connect With the Beam community
+#### Development Setup {#development-setup}
-1. Consider subscribing to the [dev@ mailing list](/community/contact-us/),
especially
- if you plan to make more than one change or the change will be large. All
decisions happen on the
- public dev list.
-1. (Optionally) Join the [#beam channel of the ASF
slack](/community/contact-us/).
-1. Create an account on [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues)
- (anyone can do this).
+1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
+<br><br>
-### Share your intent
+2. Clone the git repository. You can download it anywhere you like.
+```
+$ mkdir -p ~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+```
-1. Find or create an issue in the [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues).
- Tracking your work in an issue will avoid duplicated or conflicting work,
and provide
- a place for notes. Later, your pull request will be linked to the issue as
well.
-1. If you want to get involved but don't have a project in mind, check our
list of open starter tasks,
-
[https://s.apache.org/beam-starter-tasks](https://s.apache.org/beam-starter-tasks).
-1. Assign the issue to yourself. To get the permission to do so, email
- the [dev@ mailing list](/community/contact-us)
- to introduce yourself and to be added as a contributor in the Beam issue
tracker including your
- ASF Jira Username. For example [this welcome
email](https://lists.apache.org/thread.html/e6018c2aaf7dc7895091434295e5b0fafe192b975e3e3761fcf0cda7@%3Cdev.beam.apache.org%3E).
-1. If your change is large or it is your first change, it is a good idea to
- [discuss it on the dev@ mailing list](/community/contact-us/).
-1. For large changes create a design doc
- ([template](https://s.apache.org/beam-design-doc-template),
- [examples](https://s.apache.org/beam-design-docs)) and email it to the
[dev@ mailing list](/community/contact-us).
-### Development Setup {#development-setup}
+  For **Go development**:
-1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
-1. Clone the git repository. You can download it anywhere you like.
-
- $ mkdir -p ~/go/src/github.com/apache
- $ cd ~/go/src/github.com/apache
- $ git clone https://github.com/apache/beam
- $ cd beam
-
- - For Go development:
- We recommend putting it in your
[`$GOPATH`](https://golang.org/doc/gopath_code#GOPATH) (`$HOME/go` by default
on Unix systems).
- 1. Clone the repo, and update your branch as normal
- $ git clone https://github.com/apache/beam.git
- $ cd beam
- $ git remote add <GitHub_user>
[email protected]:<GitHub_user>/beam.git
- $ git fetch --all
- 1. Get or Update all the Go SDK dependencies
- $ go get -u ./...
-
-1. Check the environment was set up correctly.
- - **Option 1**: validate the Go, Java, and Python environments:
-
- **Important**: Make sure you have activated Python development.
+  We recommend putting it in your `$GOPATH` (`$HOME/go` by default
on Unix systems).
+
+  Clone the repo, and update your branch as normal
+
+
+```
+$ git clone https://github.com/apache/beam.git
+$ cd beam
+$ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam.git
+$ git fetch --all
+```
+
+  Get or Update all the Go SDK dependencies
+ ```
+$ go get -u ./...
+```
+<br>
+
+3. Check the environment was set up correctly.
+
+  **Option 1**: validate the Go, Java, and Python environments:
+
+  **Important**: Make sure you have activated Python development.
```
./gradlew :checkSetup
```
- - **Option 2**: Run independent checks:
- - For **Go development**:
- 1. Execute:
+
+
+  **Option 2**: Run independent checks:
+
+    For **Go development**:
```
-export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
-./gradlew :sdks:go:examples:wordCount
+export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore./gradlew
:sdks:go:examples:wordCount
```
- - For **Python development**:
- 1. Execute:
+    For **Python development**:
```
./gradlew :sdks:python:wordCount
```
- - For **Java development**:
- 1. Execute:
+    For **Java development**:
```
./gradlew :examples:java:wordCount
```
+<br>
-1. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
-
- $ ./gradlew projects
-
+4. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
Review comment:
done
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -160,102 +216,91 @@ script which is part of the Beam repo:
./start-build-env.sh
```
-### Connect With the Beam community
+#### Development Setup {#development-setup}
-1. Consider subscribing to the [dev@ mailing list](/community/contact-us/),
especially
- if you plan to make more than one change or the change will be large. All
decisions happen on the
- public dev list.
-1. (Optionally) Join the [#beam channel of the ASF
slack](/community/contact-us/).
-1. Create an account on [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues)
- (anyone can do this).
+1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
+<br><br>
-### Share your intent
+2. Clone the git repository. You can download it anywhere you like.
+```
+$ mkdir -p ~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+```
-1. Find or create an issue in the [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues).
- Tracking your work in an issue will avoid duplicated or conflicting work,
and provide
- a place for notes. Later, your pull request will be linked to the issue as
well.
-1. If you want to get involved but don't have a project in mind, check our
list of open starter tasks,
-
[https://s.apache.org/beam-starter-tasks](https://s.apache.org/beam-starter-tasks).
-1. Assign the issue to yourself. To get the permission to do so, email
- the [dev@ mailing list](/community/contact-us)
- to introduce yourself and to be added as a contributor in the Beam issue
tracker including your
- ASF Jira Username. For example [this welcome
email](https://lists.apache.org/thread.html/e6018c2aaf7dc7895091434295e5b0fafe192b975e3e3761fcf0cda7@%3Cdev.beam.apache.org%3E).
-1. If your change is large or it is your first change, it is a good idea to
- [discuss it on the dev@ mailing list](/community/contact-us/).
-1. For large changes create a design doc
- ([template](https://s.apache.org/beam-design-doc-template),
- [examples](https://s.apache.org/beam-design-docs)) and email it to the
[dev@ mailing list](/community/contact-us).
-### Development Setup {#development-setup}
+  For **Go development**:
-1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
-1. Clone the git repository. You can download it anywhere you like.
-
- $ mkdir -p ~/go/src/github.com/apache
- $ cd ~/go/src/github.com/apache
- $ git clone https://github.com/apache/beam
- $ cd beam
-
- - For Go development:
- We recommend putting it in your
[`$GOPATH`](https://golang.org/doc/gopath_code#GOPATH) (`$HOME/go` by default
on Unix systems).
- 1. Clone the repo, and update your branch as normal
- $ git clone https://github.com/apache/beam.git
- $ cd beam
- $ git remote add <GitHub_user>
[email protected]:<GitHub_user>/beam.git
- $ git fetch --all
- 1. Get or Update all the Go SDK dependencies
- $ go get -u ./...
-
-1. Check the environment was set up correctly.
- - **Option 1**: validate the Go, Java, and Python environments:
-
- **Important**: Make sure you have activated Python development.
+  We recommend putting it in your `$GOPATH` (`$HOME/go` by default
on Unix systems).
+
+  Clone the repo, and update your branch as normal
+
+
+```
+$ git clone https://github.com/apache/beam.git
+$ cd beam
+$ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam.git
+$ git fetch --all
+```
+
+  Get or Update all the Go SDK dependencies
+ ```
+$ go get -u ./...
+```
+<br>
+
+3. Check the environment was set up correctly.
+
+  **Option 1**: validate the Go, Java, and Python environments:
+
+  **Important**: Make sure you have activated Python development.
```
./gradlew :checkSetup
```
- - **Option 2**: Run independent checks:
- - For **Go development**:
- 1. Execute:
+
+
+  **Option 2**: Run independent checks:
+
+    For **Go development**:
```
-export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
-./gradlew :sdks:go:examples:wordCount
+export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore./gradlew
:sdks:go:examples:wordCount
```
- - For **Python development**:
- 1. Execute:
+    For **Python development**:
```
./gradlew :sdks:python:wordCount
```
- - For **Java development**:
- 1. Execute:
+    For **Java development**:
```
./gradlew :examples:java:wordCount
```
+<br>
-1. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
-
- $ ./gradlew projects
-
+4. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
+ ```
+$ ./gradlew projects
+ ```
Examine the available tasks in a project. For the default set of tasks, use:
Review comment:
done
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -160,102 +216,91 @@ script which is part of the Beam repo:
./start-build-env.sh
```
-### Connect With the Beam community
+#### Development Setup {#development-setup}
-1. Consider subscribing to the [dev@ mailing list](/community/contact-us/),
especially
- if you plan to make more than one change or the change will be large. All
decisions happen on the
- public dev list.
-1. (Optionally) Join the [#beam channel of the ASF
slack](/community/contact-us/).
-1. Create an account on [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues)
- (anyone can do this).
+1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
+<br><br>
-### Share your intent
+2. Clone the git repository. You can download it anywhere you like.
+```
+$ mkdir -p ~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+```
-1. Find or create an issue in the [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues).
- Tracking your work in an issue will avoid duplicated or conflicting work,
and provide
- a place for notes. Later, your pull request will be linked to the issue as
well.
-1. If you want to get involved but don't have a project in mind, check our
list of open starter tasks,
-
[https://s.apache.org/beam-starter-tasks](https://s.apache.org/beam-starter-tasks).
-1. Assign the issue to yourself. To get the permission to do so, email
- the [dev@ mailing list](/community/contact-us)
- to introduce yourself and to be added as a contributor in the Beam issue
tracker including your
- ASF Jira Username. For example [this welcome
email](https://lists.apache.org/thread.html/e6018c2aaf7dc7895091434295e5b0fafe192b975e3e3761fcf0cda7@%3Cdev.beam.apache.org%3E).
-1. If your change is large or it is your first change, it is a good idea to
- [discuss it on the dev@ mailing list](/community/contact-us/).
-1. For large changes create a design doc
- ([template](https://s.apache.org/beam-design-doc-template),
- [examples](https://s.apache.org/beam-design-docs)) and email it to the
[dev@ mailing list](/community/contact-us).
-### Development Setup {#development-setup}
+  For **Go development**:
-1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
-1. Clone the git repository. You can download it anywhere you like.
-
- $ mkdir -p ~/go/src/github.com/apache
- $ cd ~/go/src/github.com/apache
- $ git clone https://github.com/apache/beam
- $ cd beam
-
- - For Go development:
- We recommend putting it in your
[`$GOPATH`](https://golang.org/doc/gopath_code#GOPATH) (`$HOME/go` by default
on Unix systems).
- 1. Clone the repo, and update your branch as normal
- $ git clone https://github.com/apache/beam.git
- $ cd beam
- $ git remote add <GitHub_user>
[email protected]:<GitHub_user>/beam.git
- $ git fetch --all
- 1. Get or Update all the Go SDK dependencies
- $ go get -u ./...
-
-1. Check the environment was set up correctly.
- - **Option 1**: validate the Go, Java, and Python environments:
-
- **Important**: Make sure you have activated Python development.
+  We recommend putting it in your `$GOPATH` (`$HOME/go` by default
on Unix systems).
+
+  Clone the repo, and update your branch as normal
+
+
+```
+$ git clone https://github.com/apache/beam.git
+$ cd beam
+$ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam.git
+$ git fetch --all
+```
+
+  Get or Update all the Go SDK dependencies
+ ```
+$ go get -u ./...
+```
+<br>
+
+3. Check the environment was set up correctly.
+
+  **Option 1**: validate the Go, Java, and Python environments:
+
+  **Important**: Make sure you have activated Python development.
```
./gradlew :checkSetup
```
- - **Option 2**: Run independent checks:
- - For **Go development**:
- 1. Execute:
+
+
+  **Option 2**: Run independent checks:
+
+    For **Go development**:
```
-export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
-./gradlew :sdks:go:examples:wordCount
+export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore./gradlew
:sdks:go:examples:wordCount
```
- - For **Python development**:
- 1. Execute:
+    For **Python development**:
```
./gradlew :sdks:python:wordCount
```
- - For **Java development**:
- 1. Execute:
+    For **Java development**:
```
./gradlew :examples:java:wordCount
```
+<br>
-1. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
-
- $ ./gradlew projects
-
+4. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
+ ```
+$ ./gradlew projects
+ ```
Examine the available tasks in a project. For the default set of tasks, use:
-
- $ ./gradlew tasks
-
+ ```
+$ ./gradlew tasks
+ ```
For a given module, use:
Review comment:
done
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -160,102 +216,91 @@ script which is part of the Beam repo:
./start-build-env.sh
```
-### Connect With the Beam community
+#### Development Setup {#development-setup}
-1. Consider subscribing to the [dev@ mailing list](/community/contact-us/),
especially
- if you plan to make more than one change or the change will be large. All
decisions happen on the
- public dev list.
-1. (Optionally) Join the [#beam channel of the ASF
slack](/community/contact-us/).
-1. Create an account on [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues)
- (anyone can do this).
+1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
+<br><br>
-### Share your intent
+2. Clone the git repository. You can download it anywhere you like.
+```
+$ mkdir -p ~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+```
-1. Find or create an issue in the [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues).
- Tracking your work in an issue will avoid duplicated or conflicting work,
and provide
- a place for notes. Later, your pull request will be linked to the issue as
well.
-1. If you want to get involved but don't have a project in mind, check our
list of open starter tasks,
-
[https://s.apache.org/beam-starter-tasks](https://s.apache.org/beam-starter-tasks).
-1. Assign the issue to yourself. To get the permission to do so, email
- the [dev@ mailing list](/community/contact-us)
- to introduce yourself and to be added as a contributor in the Beam issue
tracker including your
- ASF Jira Username. For example [this welcome
email](https://lists.apache.org/thread.html/e6018c2aaf7dc7895091434295e5b0fafe192b975e3e3761fcf0cda7@%3Cdev.beam.apache.org%3E).
-1. If your change is large or it is your first change, it is a good idea to
- [discuss it on the dev@ mailing list](/community/contact-us/).
-1. For large changes create a design doc
- ([template](https://s.apache.org/beam-design-doc-template),
- [examples](https://s.apache.org/beam-design-docs)) and email it to the
[dev@ mailing list](/community/contact-us).
-### Development Setup {#development-setup}
+  For **Go development**:
-1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
-1. Clone the git repository. You can download it anywhere you like.
-
- $ mkdir -p ~/go/src/github.com/apache
- $ cd ~/go/src/github.com/apache
- $ git clone https://github.com/apache/beam
- $ cd beam
-
- - For Go development:
- We recommend putting it in your
[`$GOPATH`](https://golang.org/doc/gopath_code#GOPATH) (`$HOME/go` by default
on Unix systems).
- 1. Clone the repo, and update your branch as normal
- $ git clone https://github.com/apache/beam.git
- $ cd beam
- $ git remote add <GitHub_user>
[email protected]:<GitHub_user>/beam.git
- $ git fetch --all
- 1. Get or Update all the Go SDK dependencies
- $ go get -u ./...
-
-1. Check the environment was set up correctly.
- - **Option 1**: validate the Go, Java, and Python environments:
-
- **Important**: Make sure you have activated Python development.
+  We recommend putting it in your `$GOPATH` (`$HOME/go` by default
on Unix systems).
+
+  Clone the repo, and update your branch as normal
+
+
+```
+$ git clone https://github.com/apache/beam.git
+$ cd beam
+$ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam.git
+$ git fetch --all
+```
+
+  Get or Update all the Go SDK dependencies
+ ```
+$ go get -u ./...
+```
+<br>
+
+3. Check the environment was set up correctly.
+
+  **Option 1**: validate the Go, Java, and Python environments:
+
+  **Important**: Make sure you have activated Python development.
```
./gradlew :checkSetup
```
- - **Option 2**: Run independent checks:
- - For **Go development**:
- 1. Execute:
+
+
+  **Option 2**: Run independent checks:
+
+    For **Go development**:
```
-export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
-./gradlew :sdks:go:examples:wordCount
+export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore./gradlew
:sdks:go:examples:wordCount
```
- - For **Python development**:
- 1. Execute:
+    For **Python development**:
```
./gradlew :sdks:python:wordCount
```
- - For **Java development**:
- 1. Execute:
+    For **Java development**:
```
./gradlew :examples:java:wordCount
```
+<br>
-1. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
-
- $ ./gradlew projects
-
+4. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
+ ```
+$ ./gradlew projects
+ ```
Examine the available tasks in a project. For the default set of tasks, use:
-
- $ ./gradlew tasks
-
+ ```
+$ ./gradlew tasks
+ ```
For a given module, use:
-
- $ ./gradlew -p sdks/java/io/cassandra tasks
-
- For an exhaustive list of tasks, use:
-
- $ ./gradlew tasks --all
-
-1. Make sure you can build and run tests
+ ```
+$ ./gradlew -p sdks/java/io/cassandra tasks
+ ```
+ For an exhaustive list of tasks, use:
Review comment:
done
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -160,102 +216,91 @@ script which is part of the Beam repo:
./start-build-env.sh
```
-### Connect With the Beam community
+#### Development Setup {#development-setup}
-1. Consider subscribing to the [dev@ mailing list](/community/contact-us/),
especially
- if you plan to make more than one change or the change will be large. All
decisions happen on the
- public dev list.
-1. (Optionally) Join the [#beam channel of the ASF
slack](/community/contact-us/).
-1. Create an account on [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues)
- (anyone can do this).
+1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
+<br><br>
-### Share your intent
+2. Clone the git repository. You can download it anywhere you like.
+```
+$ mkdir -p ~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+```
-1. Find or create an issue in the [Beam issue tracker
(JIRA)](https://issues.apache.org/jira/projects/BEAM/issues).
- Tracking your work in an issue will avoid duplicated or conflicting work,
and provide
- a place for notes. Later, your pull request will be linked to the issue as
well.
-1. If you want to get involved but don't have a project in mind, check our
list of open starter tasks,
-
[https://s.apache.org/beam-starter-tasks](https://s.apache.org/beam-starter-tasks).
-1. Assign the issue to yourself. To get the permission to do so, email
- the [dev@ mailing list](/community/contact-us)
- to introduce yourself and to be added as a contributor in the Beam issue
tracker including your
- ASF Jira Username. For example [this welcome
email](https://lists.apache.org/thread.html/e6018c2aaf7dc7895091434295e5b0fafe192b975e3e3761fcf0cda7@%3Cdev.beam.apache.org%3E).
-1. If your change is large or it is your first change, it is a good idea to
- [discuss it on the dev@ mailing list](/community/contact-us/).
-1. For large changes create a design doc
- ([template](https://s.apache.org/beam-design-doc-template),
- [examples](https://s.apache.org/beam-design-docs)) and email it to the
[dev@ mailing list](/community/contact-us).
-### Development Setup {#development-setup}
+  For **Go development**:
-1. Check [Git workflow
tips](https://cwiki.apache.org/confluence/display/BEAM/Git+Tips) if you need
help with git forking, cloning, branching, committing, pull requests, and
squashing commits.
-1. Clone the git repository. You can download it anywhere you like.
-
- $ mkdir -p ~/go/src/github.com/apache
- $ cd ~/go/src/github.com/apache
- $ git clone https://github.com/apache/beam
- $ cd beam
-
- - For Go development:
- We recommend putting it in your
[`$GOPATH`](https://golang.org/doc/gopath_code#GOPATH) (`$HOME/go` by default
on Unix systems).
- 1. Clone the repo, and update your branch as normal
- $ git clone https://github.com/apache/beam.git
- $ cd beam
- $ git remote add <GitHub_user>
[email protected]:<GitHub_user>/beam.git
- $ git fetch --all
- 1. Get or Update all the Go SDK dependencies
- $ go get -u ./...
-
-1. Check the environment was set up correctly.
- - **Option 1**: validate the Go, Java, and Python environments:
-
- **Important**: Make sure you have activated Python development.
+  We recommend putting it in your `$GOPATH` (`$HOME/go` by default
on Unix systems).
+
+  Clone the repo, and update your branch as normal
+
+
+```
+$ git clone https://github.com/apache/beam.git
+$ cd beam
+$ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam.git
+$ git fetch --all
+```
+
+  Get or Update all the Go SDK dependencies
+ ```
+$ go get -u ./...
+```
+<br>
+
+3. Check the environment was set up correctly.
+
+  **Option 1**: validate the Go, Java, and Python environments:
+
+  **Important**: Make sure you have activated Python development.
```
./gradlew :checkSetup
```
- - **Option 2**: Run independent checks:
- - For **Go development**:
- 1. Execute:
+
+
+  **Option 2**: Run independent checks:
+
+    For **Go development**:
```
-export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
-./gradlew :sdks:go:examples:wordCount
+export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore./gradlew
:sdks:go:examples:wordCount
```
- - For **Python development**:
- 1. Execute:
+    For **Python development**:
```
./gradlew :sdks:python:wordCount
```
- - For **Java development**:
- 1. Execute:
+    For **Java development**:
```
./gradlew :examples:java:wordCount
```
+<br>
-1. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
-
- $ ./gradlew projects
-
+4. Familiarize yourself with gradle and the project structure. At the root of
the git repository, run:
+ ```
+$ ./gradlew projects
+ ```
Examine the available tasks in a project. For the default set of tasks, use:
-
- $ ./gradlew tasks
-
+ ```
+$ ./gradlew tasks
+ ```
For a given module, use:
-
- $ ./gradlew -p sdks/java/io/cassandra tasks
-
- For an exhaustive list of tasks, use:
-
- $ ./gradlew tasks --all
-
-1. Make sure you can build and run tests
+ ```
+$ ./gradlew -p sdks/java/io/cassandra tasks
+ ```
+ For an exhaustive list of tasks, use:
+ ```
+$ ./gradlew tasks --all
+ ```
+5. Make sure you can build and run tests
Review comment:
done
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
