Conversation

olavloite

Including the google-cloud-spanner test-jar in the bom will allow other libraries to use the test jar without having to specify a version. This again should prevent the kind of failures that we are currently seeing in googleapis/java-spanner-jdbc#142

(The jdbc driver currently defines a specific version for the test-jar in the pom here.)

@googlebotgooglebot added the cla: yesThis human has signed the Contributor License Agreement.label Jun 9, 2020
@olavloite

The integration test failures are not related to this change, and will be fixed by #252. The code format failure is as far as I can tell also not related to this change.

@skuruppu

Unfortunately, I don't have the permissions to force-merge if required checks fail :(

@chingor13

The lint problem should be fixed by google-cloud-shared-config 0.7.0 which is releasing now - google-java-format shipped a version incompatible with Java 8

@skuruppuskuruppu added the kokoro:force-runAdd this label to force Kokoro to re-run the tests.label Jun 11, 2020
@yoshi-kokoroyoshi-kokoro removed the kokoro:force-runAdd this label to force Kokoro to re-run the tests.label Jun 11, 2020
@skuruppuskuruppu merged commit 4e86a37 into master Jun 11, 2020
@skuruppuskuruppu deleted the include-test-jar-in-bom branch June 11, 2020 01:01
olavloite added a commit that referenced this pull request Nov 4, 2020
Some enums were defined as package-private, but these were used in the
public API of the Connection API. That made the specific methods in the
Connection API unusable from outside the Spanner client library.

Towards #253
olavloite added a commit that referenced this pull request Nov 5, 2020
Some enums were defined as package-private, but these were used in the
public API of the Connection API. That made the specific methods in the
Connection API unusable from outside the Spanner client library.

Towards #253
rajatbhatta pushed a commit to rajatbhatta/java-spanner that referenced this pull request Nov 17, 2022
* feat: expose more methods from Connection in JDBC

More methods from the Connection API should be exposed in the
Cloud Spanner JDBC Connection interface to make it easier to
execute read-only transactions with specific timestamp bounds.

Towards googleapis#253

* clirr: add ignored differences
Sign up for free to join this conversation on . Already have an account? Sign in to comment
cla: yesThis human has signed the Contributor License Agreement.
None yet

Successfully merging this pull request may close these issues.