Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing:
java_settings:
service_class_names:
The package name to use in Java. Clobbers the java_package option
set in the protobuf. This should be used only by APIs
who have already set the language_settings.java.package_name" field
in gapic.yaml. API teams should use the protobuf java_package option
where possible.
Example of a YAML configuration::
publishing:
java_settings:
library_package: com.google.cloud.pubsub.v1
The package name to use in Java. Clobbers the java_package option
set in the protobuf. This should be used only by APIs
who have already set the language_settings.java.package_name" field
in gapic.yaml. API teams should use the protobuf java_package option
where possible.
Example of a YAML configuration::
publishing:
java_settings:
library_package: com.google.cloud.pubsub.v1
Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing:
java_settings:
service_class_names:
Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing:
java_settings:
service_class_names:
Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing:
java_settings:
service_class_names:
Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing:
java_settings:
service_class_names:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[],[]]