This is an automated email from the ASF dual-hosted git repository.
bodewig pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant-ivy.git
The following commit(s) were added to refs/heads/master by this push:
new dcd36eac document what I've learned about Ivy files.
dcd36eac is described below
commit dcd36eac92a3158c5c1f90752f9d818b5277d10a
Author: Stefan Bodewig <[email protected]>
AuthorDate: Mon Feb 16 18:20:22 2026 +0100
document what I've learned about Ivy files.
---
asciidoc/ivyfile.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/asciidoc/ivyfile.adoc b/asciidoc/ivyfile.adoc
index 21954fd8..e31bceab 100644
--- a/asciidoc/ivyfile.adoc
+++ b/asciidoc/ivyfile.adoc
@@ -47,6 +47,8 @@ For those familiar with XML schema, the schema used to
validate Ivy files can be
</ivy-module>
----
+Ivy expects to use the "no namespace" namespace, so you can't use an XML
namespace to identify Ivy elements or attributes or use any namespace prefix
for Ivy's built-in elements/attributes.
+
== Dynamic and [[resolved]]resolved Ivy files
A module descriptor (Ivy file) is needed both before and after the publication
of each revision of the module. Depending on the case, a module descriptor can
be either _dynamic_ or _resolved_.