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
{{ message }}
This repository was archived by the owner on Oct 29, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 29, 2026. It is now read-only.
java_gapic_assembly_gradle_pkg rule does not generate javadocs task in client build.gradle #1367
I use bazel to build a java_gapic_assembly_gradle_pkg rule to build a java client library tar:
java_gapic_assembly_gradle_pkg(
name = "API-v1-java",
include_samples = True,
transport = "grpc+rest",
deps = [
":FOO_java_gapic",
":FOO_java_grpc",
":FOO_java_proto",
":FOO_proto",
],
)
When java_gapic_assembly_gradle_pkg is used to generate a java client library tar, if you run ./gradlew build from the top-level directory of the extracted tar, it will generate javadocs for proto and grpc, but not for the gapic client
Expected behavior:
When I run ./gradlew build from the top level directory of the extracted tar generated by the java_gapic_assembly_gradle_pkg rule, these javadocs should be generated:
It looks like these are templates that are used by the java_gapic_assembly_gradle_pkg rule to generate the build.gradle file for the gapic client, and they do not contain a task for generating javadocs.
By contrast, the gradle template files for proto and grpc do:
Activity
chore: update java template (#1367) (#627)
chore: update java template (#1367) (#749)
feat: Add JavadocJar Task to build.gradle for self service libraries (#…
feat: Add JavadocJar Task to build.gradle for self service libraries (#…