You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2025/07/31 19:23:00 UTC

[jira] [Created] (IVY-1663) ivy:checkdepsupdate latest.release includes alphas, betas, milestones and release candidates

Eric Milles created IVY-1663:
--------------------------------

             Summary: ivy:checkdepsupdate latest.release includes alphas, betas, milestones and release candidates
                 Key: IVY-1663
                 URL: https://issues.apache.org/jira/browse/IVY-1663
             Project: Ivy
          Issue Type: Bug
          Components: Ant
    Affects Versions: 2.5.3
            Reporter: Eric Milles


I have been experimenting with {{ivy:checkdepsupdate}} to get a list of dependencies that need to be updated.  The default {{revisionToCheck}} is {{latest.integration}} which includes shapshot releases.  So I set {{revisionToCheck}} to {{latest.release}} and indeed snapshots are no longer reported.  However, I am seeing alpha, beta, milestone and release candidate artifacts reported as available.  I did not choose "latest.milestone" so I'd not like to see these proposals.

As best I can figure, the status for an ibiblio repository (pom) is set in {{org.apache.ivy.plugins.parser.m2.PomModuleDescriptorBuilder#setModuleRevId}} where is looks for no version or a version ending in "SNAPSHOT" to choose "integration" or "release" status.  Can I provide rules for this in my {{ivysettings.xml}} so that I can map to "integration", "milestone" and "release" as I see fit?

Once a pom file has been saved to my local cache as an ivy.xml, it no longer consults {{PomModuleDescriptorBuilder}}.  So for cached resources, is there anything I can do to change the status value?

If status is not the way to go, it seems that my only option is to override the {{LatestVersionMatcher}} so I can inject my own rules for "release" or provide my own dynamic version matcher with some other keyword besides "latest."

Otherwise, I can't find a sensible value to put into {{revisionToCheck}} since it must apply to all dependencies.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)