This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-configuration.git
The following commit(s) were added to refs/heads/master by this push:
new eacc11863 Use HTTPS in URL
eacc11863 is described below
commit eacc11863c92a70281a0115739e9f2cabef1d491
Author: Gary Gregory <[email protected]>
AuthorDate: Sun Nov 2 10:13:02 2025 -0500
Use HTTPS in URL
---
.../java/org/apache/commons/configuration2/XMLConfiguration.java | 4 ++--
.../commons/configuration2/plist/PropertyListConfiguration.java | 2 +-
src/site/xdoc/building.xml | 2 +-
src/site/xdoc/index.xml | 6 +++---
src/site/xdoc/userguide/howto_beans.xml | 2 +-
src/site/xdoc/userguide/howto_xml.xml | 4 ++--
src/site/xdoc/userguide/upgradeto2_0.xml | 2 +-
src/site/xdoc/userguide_v1.10/howto_beans.xml | 4 ++--
src/site/xdoc/userguide_v1.10/howto_xml.xml | 4 ++--
9 files changed, 15 insertions(+), 15 deletions(-)
diff --git
a/src/main/java/org/apache/commons/configuration2/XMLConfiguration.java
b/src/main/java/org/apache/commons/configuration2/XMLConfiguration.java
index acee8b58c..9251f5df4 100644
--- a/src/main/java/org/apache/commons/configuration2/XMLConfiguration.java
+++ b/src/main/java/org/apache/commons/configuration2/XMLConfiguration.java
@@ -136,7 +136,7 @@ import org.xml.sax.helpers.DefaultHandler;
* <p>
* Per default the spaces in the {@code indent} element will be trimmed
resulting in an empty element. To tell
* {@code XMLConfiguration} that spaces are relevant the {@code xml:space}
attribute can be used, which is defined in
- * the <a href="http://www.w3.org/TR/REC-xml/#sec-white-space";>XML
specification</a>. This will look as follows:
+ * the <a href="https://www.w3.org/TR/REC-xml/#sec-white-space";>XML
specification</a>. This will look as follows:
* </p>
*
* <pre>
@@ -492,7 +492,7 @@ public class XMLConfiguration extends
BaseHierarchicalConfiguration implements F
/**
* Checks whether the content of the current XML element should be
trimmed. This method checks whether a
* {@code xml:space} attribute is present and evaluates its value. See
- * <a href="http://www.w3.org/TR/REC-xml/#sec-white-space";>
http://www.w3.org/TR/REC-xml/#sec-white-space</a> for more
+ * <a href="https://www.w3.org/TR/REC-xml/#sec-white-space";>
http://www.w3.org/TR/REC-xml/#sec-white-space</a> for more
* details.
*
* @param element the current XML element
diff --git
a/src/main/java/org/apache/commons/configuration2/plist/PropertyListConfiguration.java
b/src/main/java/org/apache/commons/configuration2/plist/PropertyListConfiguration.java
index 9a525c184..e84317767 100644
---
a/src/main/java/org/apache/commons/configuration2/plist/PropertyListConfiguration.java
+++
b/src/main/java/org/apache/commons/configuration2/plist/PropertyListConfiguration.java
@@ -51,7 +51,7 @@ import org.apache.commons.lang3.StringUtils;
* <li><a href=
*
"https://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/OldStylePlists/OldStylePLists.html";>
Apple
* Documentation - Old-Style ASCII Property Lists</a></li>
- * <li><a
href="http://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSPropertyList.html";>
GNUStep
+ * <li><a
href="https://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSPropertyList.html";>
GNUStep
* Documentation</a></li>
* </ul>
*
diff --git a/src/site/xdoc/building.xml b/src/site/xdoc/building.xml
index fcb4d0d2b..f0c1c8d87 100644
--- a/src/site/xdoc/building.xml
+++ b/src/site/xdoc/building.xml
@@ -26,7 +26,7 @@
<section name="Building">
<p>
- Commons Configuration uses <a
href="http://maven.apache.org";>Maven</a> as its build tool.
+ Commons Configuration uses <a
href="https://maven.apache.org";>Maven</a> as its build tool.
Any recent version of Maven should work. To build the Configuration
jar, change into the directory where the source distribution
resides and run
"mvn install". This will compile the source and tests, run the
tests, and then
diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index 3e119f888..a25cac6c2 100644
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -83,7 +83,7 @@ Integer integer = config.getInteger("number");
The most recent Commons Configuration 2.x release can be downloaded from
the
<a
href="https://commons.apache.org/configuration/download_configuration.cgi";>Apache
download area</a>.
The artifacts have also been deployed to
- <a href="http://repo1.maven.org/maven2/";>Maven central</a>. Commons
Configuration 1.x
+ <a href="https://repo1.maven.org/maven2/";>Maven central</a>. Commons
Configuration 1.x
artifacts are also available under their original Maven coordinates.
</p>
</section>
@@ -91,8 +91,8 @@ Integer integer = config.getInteger("number");
<section name="History">
<p>
Commons Configuration started as code in Apache JServ. The JServ code
was subsequently
- added to <a href="http://jakarta.apache.org/turbine";>Jakarta
Turbine</a>. After Jakarta
- Turbine, this configuration interface moved to <a
href="http://jakarta.apache.org/velocity";>Jakarta Velocity</a>
+ added to <a href="https://jakarta.apache.org/turbine";>Jakarta
Turbine</a>. After Jakarta
+ Turbine, this configuration interface moved to <a
href="https://jakarta.apache.org/velocity";>Jakarta Velocity</a>
and underwent various improvements. After Velocity, this code was
introduced to the
<a href="https://commons.apache.org";>Apache Commons</a> as
<code>ExtendedProperties</code>.
Configuration began life in the Commons as a Sandbox component and was
promoted to the
diff --git a/src/site/xdoc/userguide/howto_beans.xml
b/src/site/xdoc/userguide/howto_beans.xml
index 4cedfea9d..444305d1b 100644
--- a/src/site/xdoc/userguide/howto_beans.xml
+++ b/src/site/xdoc/userguide/howto_beans.xml
@@ -48,7 +48,7 @@
<p>
<em>Note: The concept of defining service objects in configuration files
and let them be created by a special container has grown popular these
- days. Especially IoC containers like <a
href="http://www.springframework.org/";>Spring</a> offer wide
+ days. Especially IoC containers like <a
href="https://www.springframework.org/";>Spring</a> offer wide
functionality related to this topic. Commons Configuration is not and has
no ambitions to become an IoC container. The provided functionality for
declaring and creating beans is very basic and limited compared to the
diff --git a/src/site/xdoc/userguide/howto_xml.xml
b/src/site/xdoc/userguide/howto_xml.xml
index aa16bae90..5b1068670 100644
--- a/src/site/xdoc/userguide/howto_xml.xml
+++ b/src/site/xdoc/userguide/howto_xml.xml
@@ -164,7 +164,7 @@ XMLConfiguration config = builder.getConfiguration();
cannot support XML documents using an XML Schema.
</p>
<p>
- <a
href="http://xml.apache.org/commons/components/resolver/resolver-article.html#s.whats.wrong";>XML
+ <a
href="https://xml.apache.org/commons/components/resolver/resolver-article.html#s.whats.wrong";>XML
Entity and URI Resolvers</a> describes using a set of catalog
files to
resolve entities. <em>Commons Configuration</em> provides support
for
this Catalog Resolver through its own
@@ -191,7 +191,7 @@ XMLConfiguration config = builder.getConfiguration();
schemas. When processing the document the parser will pass the
hint,
in this case https://commons.apache.org/sample.xsd, to the entity
resolver
as the system id. More information on using schema locations can
be found
- at <a
href="http://www.w3.org/TR/xmlschema-0/#schemaLocation";>schemaLocation</a>.
+ at <a
href="https://www.w3.org/TR/xmlschema-0/#schemaLocation";>schemaLocation</a>.
</p>
<p>
The example that follows shows how to use the
<code>CatalogResolver</code> class when
diff --git a/src/site/xdoc/userguide/upgradeto2_0.xml
b/src/site/xdoc/userguide/upgradeto2_0.xml
index ed39f84cf..a520b7015 100644
--- a/src/site/xdoc/userguide/upgradeto2_0.xml
+++ b/src/site/xdoc/userguide/upgradeto2_0.xml
@@ -95,7 +95,7 @@
this task.
</p>
<p>
- For the same reason the <a href="http://maven.apache.org";>Maven</a>
+ For the same reason the <a href="https://maven.apache.org";>Maven</a>
coordinates have been changed. Use the following dependency declaration
in your pom:
</p>
diff --git a/src/site/xdoc/userguide_v1.10/howto_beans.xml
b/src/site/xdoc/userguide_v1.10/howto_beans.xml
index e2d797c0b..b9baac3d8 100644
--- a/src/site/xdoc/userguide_v1.10/howto_beans.xml
+++ b/src/site/xdoc/userguide_v1.10/howto_beans.xml
@@ -49,8 +49,8 @@
<p>
<em>Note: The concept of defining service objects in configuration files
and let them be created by a special container has grown popular these
- days. Especially IoC containers like <a
href="http://jakarta.apache.org/hivemind/";>HiveMind</a>
- or <a href="http://www.springframework.org/";>Spring</a> offer wide
+ days. Especially IoC containers like <a
href="https://jakarta.apache.org/hivemind/";>HiveMind</a>
+ or <a href="https://www.springframework.org/";>Spring</a> offer wide
functionality related to this topic. Commons Configuration is not and has
no ambitions to become an IoC container. The provided functionality for
declaring and creating beans is very basic and limited compared to the
diff --git a/src/site/xdoc/userguide_v1.10/howto_xml.xml
b/src/site/xdoc/userguide_v1.10/howto_xml.xml
index 77ddf6347..d8d4987c8 100644
--- a/src/site/xdoc/userguide_v1.10/howto_xml.xml
+++ b/src/site/xdoc/userguide_v1.10/howto_xml.xml
@@ -1090,7 +1090,7 @@ config.load();
cannot support XML documents using an XML Schema.
</p>
<p>
- <a
href="http://xml.apache.org/commons/components/resolver/resolver-article.html#s.whats.wrong";>XML
+ <a
href="https://xml.apache.org/commons/components/resolver/resolver-article.html#s.whats.wrong";>XML
Entity and URI Resolvers</a> describes using a set of catalog
files to
resolve entities. Commons Configuration provides support for
this Catalog Resolver through its own CatalogResolver class.
@@ -1115,7 +1115,7 @@ config.load();
schemas. When processing the document the parser will pass the
hint,
in this case https://commons.apache.org/sample.xsd, to the entity
resolver
as the system id. More information on using schema locations can
be found
- at <a
href="http://www.w3.org/TR/xmlschema-0/#schemaLocation";>schemaLocation</a>.
+ at <a
href="https://www.w3.org/TR/xmlschema-0/#schemaLocation";>schemaLocation</a>.
</p>
<p>
The example that follows shows how to use the CatalogResolver when
