You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: trunk/CONTRIBUTING.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Contributing
7
7
4. Send a pull request.
8
8
9
9
10
-
Here are some guidelines for hacking on gcloud-java.
10
+
Here are some guidelines for hacking on google-cloud.
11
11
12
12
13
13
Using maven for build/test
@@ -17,26 +17,26 @@ Maven 3.0+ is required.
17
17
18
18
When downloading the source, we recommend you obtain service account credentials.
19
19
These credentials will allow you to run integration tests using `mvn verify` in command line.
20
-
Follow step 2 of the [authentication instructions](https://github.com/GoogleCloudPlatform/gcloud-java#authentication) to generate and use JSON service account credentials.
20
+
Follow step 2 of the [authentication instructions](https://github.com/GoogleCloudPlatform/google-cloud-java#authentication) to generate and use JSON service account credentials.
21
21
22
22
It's also important to test that changes don't break compatibility with App/Compute Engine and when running elsewhere.
23
-
To run tests on different platforms, try deploying the apps available on the [gcloud-java-examples](https://github.com/GoogleCloudPlatform/gcloud-java-examples) repository.
24
-
End-to-end tests should ensure that gcloud-java works when running on the
23
+
To run tests on different platforms, try deploying the apps available on the [google-cloud-examples](https://github.com/GoogleCloudPlatform/google-cloud-examples) repository.
24
+
End-to-end tests should ensure that google-cloud works when running on the
25
25
26
26
* App Engine production environment (see the docs for [uploading your app to production App Engine](https://cloud.google.com/appengine/docs/java/tools/maven#uploading_your_app_to_production_app_engine))
27
27
* App Engine development server (see the docs for [testing your app with the development server](https://cloud.google.com/appengine/docs/java/tools/maven#testing_your_app_with_the_development_server))
28
28
* Compute Engine (see the [Getting Started Guide](https://cloud.google.com/compute/docs/quickstart), and be sure to [enable the appropriate APIs](https://github.com/GoogleCloudPlatform/gcloud-common/tree/master/authentication#on-google-compute-engine))
29
29
* Your desktop (using `mvn exec:java`, for example)
30
30
31
-
When changes are made to authentication and project ID-related code, authentication and project ID inference should be tested using all relevant methods detailed in the [authentication docs](https://github.com/GoogleCloudPlatform/gcloud-java#authentication) and [project ID docs](https://github.com/GoogleCloudPlatform/gcloud-java#specifying-a-project-id).
31
+
When changes are made to authentication and project ID-related code, authentication and project ID inference should be tested using all relevant methods detailed in the [authentication docs](https://github.com/GoogleCloudPlatform/google-cloud-java#authentication) and [project ID docs](https://github.com/GoogleCloudPlatform/google-cloud-java#specifying-a-project-id).
32
32
33
33
Known issue: If you have installed the Google Cloud SDK, be sure to log in (using `gcloud auth login`) before running tests. Though the Datastore tests use a local Datastore emulator that doesn't require authentication, they will not run if you have the Google Cloud SDK installed but aren't authenticated.
34
34
35
35
**Please, do not use your production projects for executing integration tests.** While we do our best to make our tests independent of your project's state and content, they do perform create, modify and deletes, and you do not want to have your production data accidentally modified.
36
36
37
37
Adding Features
38
38
---------------
39
-
In order to add a feature to gcloud-java:
39
+
In order to add a feature to google-cloud:
40
40
41
41
The feature must be fully documented using Javadoc and examples should be provided.
42
42
The feature must work fully on Java 7 and above.
@@ -45,7 +45,7 @@ but new dependencies should be discussed).
45
45
46
46
Adding Support for a New Service
47
47
--------------------------------
48
-
See [SUPPORTING_NEW_SERVICES](./SUPPORTING_NEW_SERVICES.md) for guidelines on how to add support for a new Google Cloud service to `gcloud-java`.
48
+
See [SUPPORTING_NEW_SERVICES](./SUPPORTING_NEW_SERVICES.md) for guidelines on how to add support for a new Google Cloud service to `google-cloud-java`.
49
49
50
50
Coding Style
51
51
------------
@@ -73,4 +73,4 @@ Please note that this project is released with a Contributor Code of Conduct. By
0 commit comments