Security update for apache-ivy
This update for apache-ivy fixes the following issue:
- CVE-2026-26032: directory traversal sequences in module coordinates can allow overwriting arbitrary files outside
the configured "buildRoot" directory (bsc#1271727).
Changes for apache-ivy:
+ the ivy:retrieve task failed when the retrieve pattern
contained some text in parentheses before the first token, for
instance: /jobs/lib (JDK 17)/[artifact].[ext] (IVY-1660)
+ when the ivy:deliver task is configured to replace dynamic
revisions, it now replaces these revisions to the resolved
revision before any conflict resolution was done, which was
the original behavior before Ivy 2.3.0. This way, the
delivered ivy.xml can be used to have reproducible dependency
resolution, especially when multiple configurations are used.
It also fixes issues where the dynamic revisions were replaced
by versions from other configurations. (IVY-1485, IVY-1661)
+ the ivy:deliver task didn't replace dynamic revision from
inherited dependencies. (IVY-1410)
+ the ivy:install task didn't take the from resolver into
account when resolving Maven parent modules or
source/javadoc artifacts.
+ the ivy:checkdepsupdate task could suggest a lesser version as
update. (IVY-1665)
+ the ivy:makepom task no longer adds a dependency to the
dependencyManagement section. (IVY-1667)
+ the ivy:deliver task didn't include XML namespaces from a
parent ivy module when merging the descriptors. (IVY-1658)
+ the ivy:checkdepsupdate task no longer shows evicted versions.
(IVY-1662)
+ use Apache Commons Compress for pack200 handling to avoid
issues on Java 14 and later. If pack200 is needed, make sure
to add Apache Commons Compress to your classpath. (IVY-1652)
+ ivy:retrieve and the 'post resolve tasks' now support the
override child element. (IVY-1664)
+ ivy:makepom will now add override elements of the ivy.xml to
the dependencyManagement section of the generated pom.
(IVY-1663)
+ ivy:deliver and ivy:publish now writes inherited dependencies
first to preserve resolve order (IVY-1656)
+ ModuleRevisionId.encodeToString now returns a deterministic
string that doesn't rely on a implmentation of HashMap
+ added a new nearest conflict manager, which handles conflicts
in the same way that Maven does. (IVY-813)
