This is an automated email from the ASF dual-hosted git repository.

garydgregory pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/commons-xml.git

commit 5dd2dbfafb8f321f246e4262d1b7336d3e5b235d
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Aug 28 14:49:47 2026 -0400

    Javadoc: "hardened" -> "secure/securing" wording to match new class and
    method names.
    
    Rename test methods.
---
 src/test/java/org/apache/commons/xml/OverrideDefaultParserTest.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/src/test/java/org/apache/commons/xml/OverrideDefaultParserTest.java 
b/src/test/java/org/apache/commons/xml/OverrideDefaultParserTest.java
index b754587..1669e2e 100644
--- a/src/test/java/org/apache/commons/xml/OverrideDefaultParserTest.java
+++ b/src/test/java/org/apache/commons/xml/OverrideDefaultParserTest.java
@@ -41,7 +41,7 @@
  *
  * <p>The wrapped implementations' internal parsers are never used — the 
wrappers parse every source themselves — so instead of configuring the delegate 
the
  * wrappers read the feature: {@code false} (the JDK's default) pins the 
platform's built-in parser, {@code true} (or a delegate that does not recognize 
the
- * feature) keeps the pluggable lookup. Both choices are hardened, so the 
feature carries no security weight. The tests pin the JDK implementations 
through
+ * feature) keeps the pluggable lookup. Both choices are secure, so the 
feature carries no security weight. The tests pin the JDK implementations 
through
  * {@code newDefaultInstance()}, so they discriminate in every JVM execution; 
under test-jdk-xerces the two parser families genuinely differ.</p>
  */
 @Tag("trax")

Reply via email to