You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ant.apache.org by "Ilya (JIRA)" <ji...@apache.org> on 2015/10/05 10:45:26 UTC

[jira] [Updated] (IVY-1535) Ivy.findModule() does not invalidate artifacts

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

Ilya updated IVY-1535:
----------------------
    Attachment: patch

> Ivy.findModule() does not invalidate artifacts
> ----------------------------------------------
>
>                 Key: IVY-1535
>                 URL: https://issues.apache.org/jira/browse/IVY-1535
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0
>            Reporter: Ilya
>         Attachments: patch
>
>
> I have Java code, that at one point calls {{Ivy.findModule()}}. If there are new ivys and artifacts for this module in repository, then {{Ivy.findModule()}} updates ivys, but does not delete artifacts. Subsequent resolutions then return cached new ivys and outdated artifacts. That poses a problem.
> The proposed solution is to use {{changing=true}} in synthetic {{DependencyDescriptor}} created by {{ResolveEngine.findModule()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)