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
It also works just as well to declare a dependency only on the specific clients that you need. See the README of
75
76
each client for instructions.
76
77
78
+
If you're using IntelliJ or Eclipse, you can add client libraries to your project using these IDE plugins:
79
+
*[Cloud Tools for IntelliJ](https://cloud.google.com/tools/intellij/docs/client-libraries)
80
+
*[Cloud Tools for Eclipse](https://cloud.google.com/eclipse/docs/libraries)
81
+
82
+
Besides adding client libraries, the plugins provide additional functionality, such as service account key management. Refer to the documentation for each plugin for more details.
83
+
77
84
These client libraries can be used on App Engine standard for Java 8 runtime, App Engine flexible (including the Compat runtime). Most of the libraries do not work on the App Engine standard for Java 7 runtime, however, Datastore, Storage, and Bigquery should work.
78
85
79
86
If you are running into problems with version conflicts, see [Version Management](#version-management).
@@ -285,7 +292,7 @@ The easiest way to solve version conflicts is to use google-cloud's BOM. In Mave
Copy file name to clipboardExpand all lines: RELEASING.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,11 +109,9 @@ Go to the [releases page](https://github.com/GoogleCloudPlatform/google-cloud-ja
109
109
110
110
Ensure that the format is consistent with previous releases (for an example, see the [0.1.0 release](https://github.com/GoogleCloudPlatform/google-cloud-java/releases/tag/v0.1.0)). After adding any missing updates and reformatting as necessary, publish the draft.
111
111
112
-
11.Create a new draft for the next release. Note any commits not included in the release that have been submitted before the release commit, to ensure they are documented in the next release.
112
+
11.Run `python utilities/bump_versions.py next_snapshot patch` to include "-SNAPSHOT" in the current project version (Alternatively, update the versions in `versions.txt` to the correct versions for the next release.). Then, run `python utilities/replace_versions.py`to update the `pom.xml` files. (If you see updates in `README.md` files at this step, you probably did something wrong.)
113
113
114
-
12. Run `python utilities/bump_versions next_snapshot patch` to include "-SNAPSHOT" in the current project version (Alternatively, update the versions in `versions.txt` to the correct versions for the next release.). Then, run `python utilities/replace_versions.py` to update the `pom.xml` files. (If you see updates in `README.md` files at this step, you probably did something wrong.)
115
-
116
-
13. Create and merge in another PR to reflect the updated project version. For an example of what this PR should look like, see [#227](https://github.com/GoogleCloudPlatform/google-cloud-java/pull/227).
114
+
13. Create and merge in another PR to reflect the updated project version.
0 commit comments