You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Johan Stuyts (JIRA)" <ji...@apache.org> on 2007/01/25 10:09:49 UTC

[jira] Updated: (IVY-389) Detection of newer and better artifacts should not happen if 'checkModified' is set to 'false'

     [ https://issues.apache.org/jira/browse/IVY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Stuyts updated IVY-389:
-----------------------------

    Attachment: ivy-389.patch

This patch fixes this issues assuming the assertions from my previous comment were correct.

WARNING: I had to fix one test, ChainResolverTest.testReturnFirstWithDefaultAndCacheAndRealResolver. This means that the changes are not fully backward compatible. Suppose you have resolvers A and B, and the dependency in the cache is from B. If the same dependency is added to A and you have 'returnFirst' set to 'true' on your chain resolver, you have to set 'checkmodified' to 'true' on your chain resolver. If you don't the dependency from B in the cache is used.


> Detection of newer and better artifacts should not happen if 'checkModified' is set to 'false'
> ----------------------------------------------------------------------------------------------
>
>                 Key: IVY-389
>                 URL: https://issues.apache.org/jira/browse/IVY-389
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Johan Stuyts
>            Priority: Minor
>         Attachments: ivy-389.patch
>
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.