The pgsc module is now carried by the Maven BOM and so the generated SBOM, by the dist gathering tasks and by the OSGi scan, which picks up tls-klog as well, and the module graph and :test aggregate in the docs list it.

Author: dghgit

bom/build.gradle

@@ -10,6 +10,7 @@ dependencies {
         api(project(":util"))
         api(project(":pkix"))
         api(project(":pg"))
+        api(project(":pgsc"))
         api(project(":tls"))
         api(project(":mls"))
         api(project(":mail"))

build.gradle

@@ -343,7 +343,7 @@ test.dependsOn([':core:test', ':prov:test', ':prov:test11', ':prov:test15', ':pr
 // same packages), so it ships alongside the others here but is deliberately absent from the BOM:
 // resolving both onto one class path would be a duplicate-class mess, and the choice between them
 // is one a consumer has to make deliberately. See tls-klog/build.gradle.
-def distModules = ['core', 'util', 'prov', 'pkix', 'pg', 'tls', 'tls-klog', 'mls', 'mail', 'jmail']
+def distModules = ['core', 'util', 'prov', 'pkix', 'pg', 'pgsc', 'tls', 'tls-klog', 'mls', 'mail', 'jmail']
 
 distModules.each { evaluationDependsOn(":$it") }
 

docs/claude/architecture.md

@@ -8,6 +8,7 @@ util ── ASN.1/X.500 helpers used by pkix
 prov ── JCA/JCE provider (BouncyCastleProvider, BouncyCastlePQCProvider) — depends on core
 pkix ── X.509 / CMS / TSP / OCSP / PKCS#12 / OpenSSL PEM — depends on prov
 pg   ── OpenPGP                          — depends on prov
+pgsc ── OpenPGP smart card / token API   — depends on pg
 tls  ── TLS API + JSSE provider          — depends on prov
 mail / jmail ── S/MIME on top of CMS     — depends on pkix
 mls  ── Messaging Layer Security

docs/claude/build-and-test.md

@@ -1,6 +1,6 @@
 # Build & test
 
-The build is Gradle multi-module. **JDK 25+ is required to drive Gradle**: the `compileJava25Java` task (e.g. `prov/build.gradle`, `tls/build.gradle`) is unconditional and sets `options.release = 25`, so a Gradle daemon launched under JDK 21/17/etc. fails `:prov:compileJava25Java` with `error: release version 25 not supported`, and that failed compile can leave `core/build/classes/java/main` empty (cascading into confusing "package does not exist" errors on the next step). (Separately, JDK 21+ is the floor for the Error Prone compiler plugin, which is compiled for Java 21 / class file 65 — an older daemon fails `:core:compileJava` with `UnsupportedClassVersionError: …ErrorProneJavacPlugin … class file version 65.0 … up to <NN>.0`.) A JDK 25 is expected at `/opt/jdk-25`; drive Gradle with `JAVA_HOME=/opt/jdk-25 BC_JDK25=/opt/jdk-25 ./gradlew …`. Optional environment variables `BC_JDK8`, `BC_JDK11`, `BC_JDK17`, `BC_JDK21`, `BC_JDK25` opt in version-specific test tasks (compiled against MR-jar overlays). The default `:test` aggregates `:core:test :prov:test :prov:test11 :prov:test15 :prov:test17 :pkix:test :pg:test :tls:test :mls:test :mail:test :jmail:test`.
+The build is Gradle multi-module. **JDK 25+ is required to drive Gradle**: the `compileJava25Java` task (e.g. `prov/build.gradle`, `tls/build.gradle`) is unconditional and sets `options.release = 25`, so a Gradle daemon launched under JDK 21/17/etc. fails `:prov:compileJava25Java` with `error: release version 25 not supported`, and that failed compile can leave `core/build/classes/java/main` empty (cascading into confusing "package does not exist" errors on the next step). (Separately, JDK 21+ is the floor for the Error Prone compiler plugin, which is compiled for Java 21 / class file 65 — an older daemon fails `:core:compileJava` with `UnsupportedClassVersionError: …ErrorProneJavacPlugin … class file version 65.0 … up to <NN>.0`.) A JDK 25 is expected at `/opt/jdk-25`; drive Gradle with `JAVA_HOME=/opt/jdk-25 BC_JDK25=/opt/jdk-25 ./gradlew …`. Optional environment variables `BC_JDK8`, `BC_JDK11`, `BC_JDK17`, `BC_JDK21`, `BC_JDK25` opt in version-specific test tasks (compiled against MR-jar overlays). The default `:test` aggregates `:core:test :prov:test :prov:test11 :prov:test15 :prov:test17 :pkix:test :pg:test :pgsc:test :tls:test :tls-klog:test :mls:test :mail:test :jmail:test`.
 
 Per-module test tasks (`:util:test`, `:pkix:test`, …) restrict to `AllTest*` classes, so `--tests org.foo.SomeTest` for a non-`AllTests` class reports "No tests found"; run the aggregating suite instead, by **exact** class name (a glob like `*cms.test.AllTests` fails to match under the `AllTest*` include — `--tests org.bouncycastle.cms.test.AllTests` works).
 

osgi_scan.xml

@@ -21,9 +21,11 @@
     <jar file="${ENV.BCHOME}/jmail/build/libs/bcjmail-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/mls/build/libs/bcmls-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/pg/build/libs/bcpg-jdk18on-${version}.jar"/>
+    <jar file="${ENV.BCHOME}/pgsc/build/libs/bcpgsc-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/pkix/build/libs/bcpkix-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/prov/build/libs/bcprov-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/tls/build/libs/bctls-jdk18on-${version}.jar"/>
+    <jar file="${ENV.BCHOME}/tls-klog/build/libs/bctls-klog-jdk18on-${version}.jar"/>
     <jar file="${ENV.BCHOME}/util/build/libs/bcutil-jdk18on-${version}.jar"/>
 
     <bundle matches="^bcprov" version="${bundle_ver}">