[jira] Commented: (IVY-938) Fixed name snapshots are not updated even if they are marked as changing and the publication date is changed in repo

["Dimitris Mouchritsas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990057#comment-12990057 ] 

Dimitris Mouchritsas commented on IVY-938:
------------------------------------------

Hi all, 
we've been having a similar problem with ivy 2.2.0. We are publishing an artifact with the following target:

    <target name="publish" description="Publish the ear to Nexus" depends="make">
        <ivy:publish organisation="com.company" module="mymodule" revision="1.0-SNAPSHOT" 
            srcivypattern="${basedir}/ivy.xml" artifactspattern="${dist.dir}/${project.artifact.name}"
            publishivy="false" conf="master" resolver="my-repo" overwrite="true">
        </ivy:publish>
    </target>

then in another project we have this dependency in ivy.xml: 

<dependency org="com.company" name="mymodule" rev="1.0-SNAPSHOT" conf="base-prepare->default" changing="true">
  <artifact name="mymodule" type="ear"/>
</dependency>

We don't expect the version to change much yet, so I have set the changing="true" to check for newer revisions with the same version. This works on my workstation (Ubuntu 10.04) but on 2 windows pc's with windows xp, ivy fails to download the latest artifact and instead gets it from the local cache. 

Currently as a workaround I have created an ant target to delete the ear file from ivy's local cache directory, but any idea why this occurs?




> Fixed name snapshots are not updated even if they are marked as changing and the publication date is changed in repo
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-938
>                 URL: https://issues.apache.org/jira/browse/IVY-938
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core, Maven Compatibility
>    Affects Versions: 2.0-RC1
>            Reporter: Jyri Kytömäki
>         Attachments: CacheUpdateTest.zip, CacheUpdateTest2.zip, ivysettings.xml
>
>
> Snapshot releases with static name like 1.2.3-SNAPSHOT are not updated into the cache.
> Same problem is with ivy and maven remote repos.
> Here ivy example:
> Remote ivy repo contains in ivy xml:
> status="integration" publication="20081010104634"
> Cache contains (.xml):
> status="integration" publication="20081010095107"
> But  ivy_resolve does not update the cache. It prints this with verbose output:
> [ivy-resolve] default: Checking cache for: dependency: org#>module;1.2.3-SNAPSHOT {runtime=[runtime]}
> [ivy-resolve] don't use cache for org#>module;1.2.3-SNAPSHOT: changing=true
> [ivy-resolve] local: Checking cache for: dependency: org#>module;1.2.3-SNAPSHOT{runtime=[runtime]}
> [ivy-resolve] local: module revision found in cache: org#>module;1.2.3-SNAPSHOT
> [ivy-resolve]   found org#>module;1.2.3-SNAPSHOT in remote_ivy
> ...
> [ivy-resolve] :: downloading artifacts ::
> [ivy-resolve]   [NOT REQUIRED] org#>module;1.2.3-SNAPSHOT!module.jar

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira