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
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
