Repository navigation
v4.0.1
Stable JPMS module identities
SMTP Connection Pool 4.0.1 gives every published JAR a stable Automatic-Module-Name, so applications can place the complete pool stack on the Java module path without depending on filename-derived names:
| Artifact | Module name |
|---|---|
smtp-connection-pool |
org.simplejavamail.smtpconnectionpool |
smtp-connection-pool-jakarta-provider |
org.simplejavamail.smtpconnectionpool.jakarta |
smtp-connection-pool-camel |
org.simplejavamail.smtpconnectionpool.camel |
The transitive object-pool chain is stable too: this release consumes clustered-object-pool 4.0.3 (org.bbottema.clusteredobjectpool), which consumes generic-object-pool 2.4.2 (org.bbottema.genericobjectpool).
Compatibility
This is a packaging-focused patch. Existing direct-pool, Jakarta smtppool, Spring, and Camel APIs and coordinates are unchanged. The core pool and Jakarta provider remain Java 8 compatible; the optional Camel adapter remains Java 17+ for Camel 4.21.x.
Simple Java Mail 9.3.0 can consume this fixed chain for its public batch-module orchestration API in #698. No Angus change is required for that work; physical-transport optimizations remain separate in #699.
Published artifacts
org.simplejavamail:smtp-connection-pool:4.0.1org.simplejavamail:smtp-connection-pool-jakarta-provider:4.0.1org.simplejavamail:smtp-connection-pool-camel:4.0.1org.simplejavamail:smtp-connection-pool-parent:4.0.1
See the pool-orchestration chooser and JPMS reference.
Closes #11.