Java: support multiple versions per release#74
Java: support multiple versions per release#74JustinBeckwith merged 16 commits intogoogleapis:masterfrom
Conversation
googlebot
added
the
cla: yes
|
@theacodes @busunkim96 As I'm not a pythonista yet, should I break the internal classes in here into separate files? |
|
What would the usage look like in gax-java? |
|
I haven't looked into the gradle release process yet. |
|
I don't think it needs to be built into the gradle release process yet; the question was more about how the direct commands would look. |
|
@garrettjonesgoogle I meant looking into how gradle handles release and snapshot versioning. The releasetool workflow should be identical. |
|
@chingor13 Ok. So what commands would I run manually to invoke the bump & replace-versions logic? |
|
If you want to separate the steps, you can do so by replying no to selective prompts. Both scenarios would start with If you want to just bump, you can say yes to updating If you want to just replace the versions, you can say no to updating |
chingor13
changed the title
|
This is ready to go whenever. |
5 participants
Java publishes packages together and different artifacts are versioned independently. We already have precedent in google-cloud-java to manage all versions in a
versions.txtfile at the root directory and to be able to annotate places to replace throughout theREADME.mdandpom.xmlfiles.This PR replaces the current
utilites/bump_versions.pyandutilities/replace_versions.pyscripts in google-cloud-java so they can be used with other repositories like gax-java.The workflow is now:
See googleapis/google-cloud-java#3777
This should make releasetool work for all of google-cloud-java, gax-java, google-auth-library-java, google-api-java-client, google-http-java-client, google-oauth-java-client.