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

maartenc 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 788c011d Updated release notes with recent merges
788c011d is described below

commit 788c011d3728f64b301faf0db127c8f22754d989
Author: Maarten Coene <[email protected]>
AuthorDate: Thu Jun 25 23:45:04 2026 +0200

    Updated release notes with recent merges
---
 asciidoc/release-notes.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/asciidoc/release-notes.adoc b/asciidoc/release-notes.adoc
index e65144e2..f2dbe228 100644
--- a/asciidoc/release-notes.adoc
+++ b/asciidoc/release-notes.adoc
@@ -57,6 +57,7 @@ Note, if you have resolved dependencies with version of Ivy 
prior to 2.6.0, you
 - IMPROVEMENT: `ivy:retrieve` and the 'post resolve tasks' now support the 
`override` child element. (IVY-1664)
 - IMPROVEMENT: `ivy:makepom` will now add `override` elements of the `ivy.xml` 
to the `dependencyManagement` section of the
   generated pom. (IVY-1663) (Thanks to Eric Milles)
+- IMPROVEMENT: `ivy:deliver` and `ivy:publish` now writes inherited 
dependencies first to preserve resolve order (IVY-1656) (Thanks to Eric Milles)
 - FIX: improved Maven dependencyManagement matching for dependencies with a 
non-default type or classifier (IVY-1654) (Thanks to Mark Kittisopikul)
 - FIX: 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)
 - FIX: 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.

Reply via email to