This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
commit d1129482fdeb6a7bd6b831d69e9d9a677daf86fa Author: Robert Lazarski <[email protected]> AuthorDate: Mon Sep 7 04:04:01 2026 -1000 Correct the mail deprecation note after unbundling The note still said the module ships in the WAR to every deployment regardless, which stopped being true when it was dropped from axis2.war in this release. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> --- src/site/markdown/release-notes/2.0.2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/site/markdown/release-notes/2.0.2.md b/src/site/markdown/release-notes/2.0.2.md index 94eb6217ce..01216f975d 100644 --- a/src/site/markdown/release-notes/2.0.2.md +++ b/src/site/markdown/release-notes/2.0.2.md @@ -120,9 +120,9 @@ service that had metadata exposure turned off, they no longer will. project-wide sweep (the jakarta rename, the SecurityManager removal, a package move) or a test-dependency bump. - It is not enabled by any default `axis2.xml`, but `axis2-webapp` depends on it, so - the module and its mail provider ship in the WAR and the binary distribution to every - deployment regardless. Its correlation of responses to requests by `In-Reply-To` + It is not enabled by any default `axis2.xml`, and as of this release it is no longer + bundled in `axis2.war` either -- it remains in `lib/` of the binary distribution for + anyone who configures it. Its correlation of responses to requests by `In-Reply-To` (`SynchronousCallback` and the callback table in `AbstractTransportListener`) is the only such mechanism in the tree and is used by nothing else; the module's own source carries long-standing `FIXME` comments saying that machinery does not belong where it
