Uploaded image for project: 'Ivy'
  1. Ivy
  2. IVY-389

Detection of newer and better artifacts should not happen if 'checkModified' is set to 'false'

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.4.1
    • 2.0.0-beta-2
    • Core
    • None

    Description

      With 'checkModified' set to 'false' Ivy still looks for an artifact in repositories when there is a copy of the artifact in the cache. The repositories that are searched are the ones that are specified before the repository from which the copy in the cache was retrieved. The latter is not contacted.

      The above happens when 'returnFirst' is set to 'true' on the chain of repositories.

      Here is some example output from a build:
      local: no ivy file nor artifact found for [ javax.jdo | jdo2-api | 2.0 ]
      tried C:\home\jstuyts\data\ivy\hippo-open-source\local/javax.jdo/jdo2-api/2.0/ivy-2.0.xml
      tried C:\home\jstuyts\data\ivy\hippo-open-source\local/javax.jdo/jdo2-api/2.0/jdo2-api-2.0.jar
      CLIENT ERROR: Not Found url=http://repository.hippocms.org/ivy/javax.jdo/jdo2-api/2.0/ivy-2.0.xml
      CLIENT ERROR: Not Found url=http://repository.hippocms.org/ivy/javax.jdo/jdo2-api/2.0/jdo2-api-2.0.jar
      hipporep: no ivy file nor artifact found for [ javax.jdo | jdo2-api | 2.0 ]
      tried http://repository.hippocms.org/ivy/javax.jdo/jdo2-api/2.0/ivy-2.0.xml
      tried http://repository.hippocms.org/ivy/javax.jdo/jdo2-api/2.0/jdo2-api-2.0.jar
      hippomavenrep: revision in cache: [ javax.jdo | jdo2-api | 2.0 ]
      found [ javax.jdo | jdo2-api | 2.0 ] in hippomavenrep

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            xavier Xavier Hanin
            jstuyts Johan Stuyts
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment