incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Faucherand (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-407) publication dates in latest-time conflict resolution are not used
Date Mon, 26 Feb 2007 17:08:05 GMT

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

Gilles Faucherand commented on IVY-407:
---------------------------------------

I tried the latest code by checkouting the subversion project and making "ant jar" and using
the ivy.jar from build/artifact/ directory. Is it the good way ? 
(I didn't find a nightly build with your last modifications at http://incubator.apache.org/ivy/downloads/latest/)

[configure] :: Ivy local-20070226105904 - 20070226105904 :: http://incubator.apache.org/ivy/
::

Well, my previous example works well now, but it was a simple example without "cascade dependencies".
I could not try our latest code in real life because I found a new bug, here a more complicated
example revealing the bug:

There are 5 modules A, B, C, D and E.
1) publish C-1.0.0, C-1.0.1and C-1.0.2
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.2 (!!!CHANGED!!!) : retrieve ok and publish A-1.0.0
4) D needs C-1.0.1 : retrieve ok and publish D-1.0.0
5) E needs D-1.0.0 and A-1.0.0 (D before A in ivy file, important again!) retrieve failed
to get C-1.0.2 from A
(get apparently C-1.0.1 from D)

  [resolve]     :: evicted modules:
  [resolve]     [ MyCompany | C | 1.0.0 ] by [[ MyCompany | C | 1.0.1 ]] in [all]
  [resolve]       in [ MyCompany | B | 1.0.0 ] with latest-time
  [resolve]     [ MyCompany | C | 1.0.2 ] by [[ MyCompany | C | 1.0.1 ]] in [all]
  [resolve]       in [ MyCompany | A | 1.0.0 ] with latest-time

Dates from repository :
  <info organisation="MyCompany" module="C" revision="1.0.0" status="integration" publication="20070226112211"/>
  <info organisation="MyCompany" module="C" revision="1.0.1" status="integration" publication="20070226112225"/>
  <info organisation="MyCompany" module="C" revision="1.0.2" status="integration" publication="20070226112233"/>


> 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
>
>
> 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.


Mime
View raw message