docs(java): Update readme with badge, add Java readme, and add a publish script for later

Author: yesudeep

README.md

@@ -1,6 +1,7 @@
 [![Go checks](https://github.com/google/dotprompt/actions/workflows/go.yml/badge.svg)](https://github.com/google/dotprompt/actions/workflows/go.yml)
 [![Python checks](https://github.com/google/dotprompt/actions/workflows/python.yml/badge.svg)](https://github.com/google/dotprompt/actions/workflows/python.yml)
 [![JS checks](https://github.com/google/dotprompt/actions/workflows/test.yml/badge.svg)](https://github.com/google/dotprompt/actions/workflows/test.yml)
+[![Java checks](https://github.com/google/dotprompt/actions/workflows/java.yml/badge.svg)](https://github.com/google/dotprompt/actions/workflows/java.yml)
 [![Ask Codewiki](https://codewiki.google/github.com/google/dotprompt)](https://codewiki.google/github.com/google/dotprompt)
 [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/google/dotprompt)
 

java/README.md

@@ -0,0 +1,119 @@
+# Java Dotprompt
+
+This directory contains the Java implementation of the Dotprompt library.
+
+## Usage
+
+Add the following dependency to your project:
+
+**Maven:**
+```xml
+<dependency>
+    <groupId>com.google.dotprompt</groupId>
+    <artifactId>dotprompt</artifactId>
+    <version>0.1.0</version>
+</dependency>
+```
+
+**Gradle:**
+```groovy
+implementation 'com.google.dotprompt:dotprompt:0.1.0'
+```
+
+**Bazel:**
+```starlark
+maven_install(
+    artifacts = [
+        "com.google.dotprompt:dotprompt:0.1.0",
+    ],
+    # ...
+)
+```
+
+## Building
+
+```bash
+bazel build //java/com/google/dotprompt:dotprompt
+```
+
+## Testing
+
+```bash
+bazel test //java/com/google/dotprompt/...
+```
+
+---
+
+# Deploying to Maven Central
+
+This section describes the process for releasing the `dotprompt` Java library to Maven Central.
+
+## Prerequisites
+
+1.  **GPG Keys**: You need a GPG key pair to sign artifacts.
+    *   Export the private key: `gpg --armor --export-secret-keys <KEY_ID>`
+    *   Note the passphrase.
+
+2.  **Sonatype OSSRH Account**: You need an account on [s01.oss.sonatype.org](https://s01.oss.sonatype.org/) with access to the `com.google.dotprompt` group ID.
+
+## GitHub Secrets Configuration
+
+Configure these secrets in the repository settings (Settings → Secrets and variables → Actions):
+
+| Secret Name | Description |
+|-------------|-------------|
+| `OSSRH_USERNAME` | Your Sonatype username |
+| `OSSRH_TOKEN` | Your Sonatype password or user token |
+| `MAVEN_GPG_PRIVATE_KEY` | ASCII-armored GPG private key |
+| `MAVEN_GPG_PASSPHRASE` | Passphrase for your GPG key |
+
+## Release Process
+
+### 1. Update the Version
+
+Before creating a release, update the version in `java/com/google/dotprompt/BUILD.bazel`:
+
+```starlark
+java_export(
+    name = "dotprompt_pkg",
+    maven_coordinates = "com.google.dotprompt:dotprompt:X.Y.Z",  # Update this
+    # ...
+)
+```
+
+### 2. Create a GitHub Release
+
+1.  Go to the **Releases** section on GitHub.
+2.  Click **Draft a new release**.
+3.  Create a new tag matching the version (e.g., `java-v0.1.0`).
+4.  Add release notes.
+5.  **Publish** the release.
+
+### 3. Automated Publishing
+
+The `Publish Java Package` workflow (`.github/workflows/publish_java.yml`) triggers automatically when a release is created:
+
+1.  Sets up JDK 21 and Bazel.
+2.  Imports the GPG key.
+3.  Runs `scripts/publish-java.sh` to publish to Maven Central.
+
+### 4. Verification
+
+*   Check the GitHub Actions workflow logs for success.
+*   Log in to [Sonatype OSSRH](https://s01.oss.sonatype.org/) to verify the staging repository.
+*   After sync (typically 10-30 minutes), verify on [Maven Central](https://search.maven.org/search?q=g:com.google.dotprompt).
+
+## Local Testing (Dry Run)
+
+To verify artifacts build correctly without publishing:
+
+```bash
+bazel build //java/com/google/dotprompt:dotprompt_pkg
+```
+
+To inspect the generated POM:
+
+```bash
+bazel build //java/com/google/dotprompt:dotprompt_pkg-pom
+cat bazel-bin/java/com/google/dotprompt/dotprompt_pkg-pom.xml
+```

scripts/publish-java.sh

@@ -0,0 +1,47 @@
+#!/bin/bash
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# SPDX-License-Identifier: Apache-2.0
+
+set -e
+
+# Usage: ./scripts/publish-java.sh <gpg_sign_key_path> <gpg_passphrase> <maven_user> <maven_password>
+
+if [ "$#" -ne 4 ]; then
+    echo "Usage: $0 <gpg_sign_key_path> <gpg_passphrase> <maven_user> <maven_password>"
+    exit 1
+fi
+
+GPG_KEY_PATH=$1
+GPG_PASSPHRASE=$2
+MAVEN_USER=$3
+MAVEN_PASSWORD=$4
+
+# Define the deployment repository URL (Sonatype OSSRH)
+DEPLOY_ENV="release" # or "snapshot" if desired, but typically we want release for tags.
+# Bazel java_export allows specifying deployment via flags or properties.
+# We will use the standard command structure generated by java_export.
+
+echo "Publishing Java artifacts..."
+
+bazel run //java/com/google/dotprompt:dotprompt_pkg.publish -- \
+    --define "maven_repo=https://oss.sonatype.org/service/local/staging/deploy/maven2/" \
+    --define "maven_user=$MAVEN_USER" \
+    --define "maven_password=$MAVEN_PASSWORD" \
+    --define "gpg_sign=true" \
+    --define "gpg_key=$GPG_KEY_PATH" \
+    --define "gpg_passphrase=$GPG_PASSPHRASE"
+
+echo "Publishing complete."