From 6675620d3f8e7c70b84faf4678f86a0324f8c917 Mon Sep 17 00:00:00 2001 From: Thomas Crowley Date: Wed, 8 Jan 2025 17:03:40 +1100 Subject: [PATCH] Update javadoc.sh --- scripts/javadoc.sh | 2 ++ src/java/io/factorhouse/kpow/key/ClientIdKeyStrategy.java | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/scripts/javadoc.sh b/scripts/javadoc.sh index 32ae98d..af8be2a 100755 --- a/scripts/javadoc.sh +++ b/scripts/javadoc.sh @@ -4,6 +4,8 @@ set -euo pipefail IFS=$'\n\t' +mkdir -p target/javadoc-out + # Run the javadoc command with the -quiet option OUTPUT=`javadoc -quiet -classpath "$(lein classpath)" -Xdoclint:all -d target/javadoc-out $(find src -name "*.java") 2>&1` diff --git a/src/java/io/factorhouse/kpow/key/ClientIdKeyStrategy.java b/src/java/io/factorhouse/kpow/key/ClientIdKeyStrategy.java index 5949298..a893594 100644 --- a/src/java/io/factorhouse/kpow/key/ClientIdKeyStrategy.java +++ b/src/java/io/factorhouse/kpow/key/ClientIdKeyStrategy.java @@ -7,7 +7,7 @@ *

This strategy simplifies the configuration process by relying solely on the client ID * and application ID, eliminating the need for a Kafka {@link org.apache.kafka.clients.admin.AdminClient}. * It is particularly suitable for constrained environments where creating an {@code AdminClient} - * may not be feasible or appropriate due to resource limitations or security concerns.

+ * may not be feasible or appropriate due to security concerns.

* *

Important: In a multi-cluster Kpow deployment, where the same application ID and client ID * are used across multiple environments (e.g., staging, development, production), this strategy