You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2010/05/07 22:14:54 UTC

[jira] Updated: (IVY-1133) ChainResolver Checkmodified override bug

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

Maarten Coene updated IVY-1133:
-------------------------------

    Fix Version/s: 2.2.0-RC1
                       (was: trunk)

> ChainResolver Checkmodified override bug
> ----------------------------------------
>
>                 Key: IVY-1133
>                 URL: https://issues.apache.org/jira/browse/IVY-1133
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0-RC2
>            Reporter: jaco uys
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>         Attachments: Checkmodified.patch
>
>
> I have found an issue some time ago with resolving dependencies via a
> chain resolver.
> I can not remember the exact scenario, but had to do with resolving A
> -> B -> C where A and C comes from a local repo and B from a 'shared'
> repo.
> The issue seems to be with ChainResolver that overrides 'public void
> setCheckmodified(boolean check)'. The 'checkModified' value is not
> propagated through to the base class 'AbstractResolver'. This results
> in the 'AbstractResolver.getCacheOptions(ResolveData data)' behaving
> incorrectly when creating the 'CacheMetadataOptions'.
> The fix I made was to change the 'ChainResolver.setCheckmodified' to:
> public void setCheckmodified(boolean check) {
>        checkmodified = Boolean.valueOf(check);
>        super.setCheckmodified(check);
> }
> I've attached an svn patch for it.

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