+1, all checks out. Thanks Gary!!!

Cheers,
-Rob

> On Nov 11, 2026, at 7:09 AM, Gary Gregory <[email protected]> wrote:
> 
> We have fixed a few bugs since the release of Apache Commons Secure
> XML 1.1.0, so I would like to release Apache Commons Secure XML 1.1.1.
> 
> Apache Commons Secure XML 1.1.1 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1
> (SVN revision 89256)
> 
> The Git tag commons-secure-xml-1.1.1-RC1 commit for this RC is
> daaaa2141a86b3e27223fb4c549568df825be411, which you can browse here:
>    
> https://gitbox.apache.org/repos/asf?p=commons-secure-xml.git;a=commit;h=daaaa2141a86b3e27223fb4c549568df825be411
> You may check out this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-secure-xml.git
> --branch commons-secure-xml-1.1.1-RC1 commons-secure-xml-1.1.1-RC1
> 
> Maven artifacts are here:
>    
> https://repository.apache.org/content/repositories/orgapachecommons-1975/org/apache/commons/commons-secure-xml/1.1.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Wed Nov 11 12:05:06 UTC 2026
> commons-secure-xml-1.1.1-bin.tar.gz=64a89d2a135a4a26142e44a63268b5f5594bad88bf90f649d5dd8c06bba7c4bbc117e6cdafec94fcd319aebca2327dbc551539379d3dcb57f0dfbf89fed74ecb
> commons-secure-xml-1.1.1-bin.zip=42411fff29f4e5c0b2b601143a074435267ebbd597e030a5541d45ddf5f63f59b189d2542b3976810a46935a1fad0addd6bd1f6cf6ec53b2acc7307a24abeaf9
> commons-secure-xml-1.1.1-bom.json=5142999b21224a69945a7afe19233ce77108f7e9eb8fafed515523e61d8fbc842b8facb1e3612e04f1ba5ce66b0142405b08e0dfb0d55d7d9ab40dbd1bf7132b
> commons-secure-xml-1.1.1-bom.xml=ecce530459011dea13b3f086e4fe3d2688eb2ee7d9a15505e16aa1a757c2fc50bdf700162551bda1ddf3330535d1a42d88ee5c2158a6bf0d734082bfb151983b
> commons-secure-xml-1.1.1-javadoc.jar=7456be86f4bf592568f5278ee16a5c44699104289a0f80765f3ae6dcc68ce6063aa6ae6e854e178e2951dccd3e38cddd1080964cf40e77541bd3ce6cb9cf490a
> commons-secure-xml-1.1.1-sources.jar=f67f76b7e958452a38e11e56867fd81e0f107e0d5395b5ef961af37c0fca1fa88c95bea0b269e30aa722f305e21863550871b9bbc3a5d784fd222e7c983a9438
> commons-secure-xml-1.1.1-src.tar.gz=61f3faee136a4aa9dde49ccbee67465fa537b8ddbe8c80089dc70893d9ee3d565358c74b5ad5a4cb6e94c751911f5ad019fe3913ccc15abb8e506cde1147dc59
> commons-secure-xml-1.1.1-src.zip=d9624bc3a319f6340890b06ff99c35c843a7a1b50c1dcdd7538fa8c90728a5147af51fcdec58e8fecf1668f13bcbecafa256aea778bfb67b5644eaf9e89b0362
> commons-secure-xml-1.1.1-test-sources.jar=dbf513101299e2bfe5ce7988fe71aa7bcb9a8e83fa45193f8a1786249b824a60d776ee5a98c4a114197f96580d622b4b611b5624a3161c16a44b6f5731acca35
> commons-secure-xml-1.1.1.jar=3952cbac7dfb25f7e435b309ab6e682ddd9ee9470624dca0ff709ec0f0a7f55ead5f935bfa1e1b4c322a26cdc20f7137e2ff7a95a70f21d0f66473a7101b1441
> commons-secure-xml-1.1.1.pom=5b92288e3be8a747f5b5d133b853c9caf8c8bfa14e03e34bde246ed971fb05448f579c1ddf63881264c2525b16afa442e193e2ba4802f9ad81246768f820d1ee
> org.apache.commons_commons-secure-xml-1.1.1.spdx.json=5b1fa5a2e5e1bc3b56025cec17344339fbca16367ad07fa7fb9794f5ef0619eed2623fccef4016d9087b2d97a3f7c879278605684e338b9196468548a3f96ff5
> 
> 
> 
> I have tested this with 'mvn' and 'mvn clean install site' using:
> 
> openjdk version "27.0.1.0.3" 2026-10-24
> OpenJDK Runtime Environment Homebrew (build 27.0.1.0.3)
> OpenJDK 64-Bit Server VM Homebrew (build 27.0.1.0.3, mixed mode, sharing)
> 
> Apache Maven 3.10.0 (c43a36b8d67be7e0805a411bc0898af1a51f5472)
> Maven home: /opt/homebrew/Cellar/maven/3.10.0/libexec
> Java version: 27.0.1.0.3, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk/27.0.1.0.3/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8, time zone: UTC
> OS name: "mac os x", version: "26.7.3", arch: "aarch64", family: "mac"
> 
> Darwin ***.local 25.6.0 Darwin Kernel Version 25.6.0: Mon Oct 12
> 00:39:48 PDT 2026; root:xnu-12377.161.15.701.48~2/RELEASE_ARM64_T6041
> arm64
> 
> Docker version 29.9.3, build 5457199
> 
> 
> Details of changes since 1.1.0 are in the release notes:
>    
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/RELEASE-NOTES.txt
>    
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/site/changes.html
> 
> Site:
>    
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/site/index.html
>    (Note some *relative* links are broken and the 1.1.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.1.0):
>    
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/site/japicmp.html
> 
> RAT Report:
>    
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Thank you,
> 
> Gary Gregory,
> Release Manager (using key 530AA5F25C25011F)
> 
> The following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==============================
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, and Maven.
> 
> You can validate a release from a release candidate (RC) tag as follows.
> 
> 1a) Download and decompress the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/secure-xml/1.1.1-RC1/source
> 
> 1b) Check out the RC tag from Git (optional)
> 
> This is optional, as a reviewer must at least check source distributions.
> 
> git clone https://gitbox.apache.org/repos/asf/commons-secure-xml.git
> --branch commons-secure-xml-1.1.1-RC1 commons-secure-xml-1.1.1-RC1
> cd commons-secure-xml-1.1.1-RC1
> 
> 2) Check the build
> 
> All components should include a default Maven goal, such that you can
> run 'mvn' from the command line by itself.
> 
> 3) Check Apache licenses
> 
> This step is not required if the site includes a RAT report page,
> which you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
> 
> mvn apache-rat:check
> 
> 4) Check binary compatibility
> 
> This step is not required if the site includes a JApiCmp report page,
> which you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
> 
> mvn verify -DskipTests -P japicmp japicmp:cmp
> 
> 5) Build the package
> 
> This check should be included in the default Maven build, but you can
> check it with:
> 
> mvn -V clean package
> 
> You can record the Maven and Java versions produced by -V in your VOTE reply.
> To gather OS information from a command line:
> Windows: ver
> Linux: uname -a
> 
> 6) Check reproducibility
> 
> To check that a build is reproducible, run:
> 
> # Verify using a JDK major version matching: 27.0.1.0.3
> export TZ="UTC"
> mvn clean verify artifact:compare -DskipTests
> -Dreference.repo=https://repository.apache.org/content/repositories/staging/
> '-Dbuildinfo.ignore=*/*.spdx.json'
> 
> Note that this excludes SPDX files from the check.
> 
> 7) Build the site for a single-module project
> 
> Note: Some plugins require the components to be installed instead of packaged.
> 
> mvn site
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
> 
> -the end-
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to