[
https://issues.apache.org/jira/browse/IVY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478698
]
Gilles Scokart commented on IVY-407:
------------------------------------
It failed also in gump :
<testcase
classname="org.apache.ivy.plugins.conflict.LatestConflictManagerTest"
name="testLatestTimeTransitivity" time="0.189">
<failure message="C revision should be 1.0.2 expected:<...2> but
was:<...0>"
type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: C
revision should be 1.0.2 expected:<...2> but was:<...0>
at
org.apache.ivy.plugins.conflict.LatestConflictManagerTest.testLatestTimeTransitivity(LatestConflictManagerTest.java:165)
See
http://vmgump.apache.org/gump/public/ivy/ivy-tests/gump_file/TEST-org.apache.ivy.plugins.conflict.LatestConflictManagerTest.xml.html
> publication dates in latest-time conflict resolution are not used
> -----------------------------------------------------------------
>
> Key: IVY-407
> URL: https://issues.apache.org/jira/browse/IVY-407
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 1.4.1, 1.5
> Environment: - Linux Fedora Core 6
> - java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> - FileSystem repository
> Reporter: Gilles Faucherand
> Assigned To: Xavier Hanin
> Fix For: 1.5
>
> Attachments: ivy-latest-time-transitivity.xml,
> ivyconf-latest-time-transitivity.xml, ivyconf-latest-time-transitivity.xml,
> LatestConflictManagerTest.java, myrepos.tgz
>
>
> I have some problems with eviction strategy, conflict resolution do not
> retrieve
> the last in time artifact published whereas the publication date are correct
> in the ivy
> file of the repository.
> Reproduce the bug:
> Set a defaultConflictManager="latest-time" in the ivyconf file
> There are 3 modules A, B and C.
> 1) publish C-1.0.0 and later C-1.0.1
> 2) B needs C-1.0.0 : retrieve (ok) and publish B-1.0.0
> 3) A needs B-1.0.0 and C-1.0.1 : (order is important: B before C in A module
> ivy file...)
> then retrieve, we get C-1.0.0 whereas it should be C-1.0.1 (latest in time)
> I do not set publication date in the module ivy file (boring to change all
> the time) or in
> the call of the publish task (attribute pubdate), Should I ?
> Anyway the publication dates have been set (by publish task ?) in the ivy
> files of the repository and they
> are different ... and not used ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.