You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jacob Aleksynas (JIRA)" <ji...@apache.org> on 2012/08/15 02:54:38 UTC
[jira] [Updated] (IVY-1176) Problem with resolve (ivy.deps.changed)
and timestamp of ivy.xml of dependencies
[ https://issues.apache.org/jira/browse/IVY-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Aleksynas updated IVY-1176:
---------------------------------
Comment: was deleted
(was: I will consistently get ivy.deps.changed=true despite certainty that the deps have not changed, I am not sure how this flag relates to the various caches (if I remove the copy in the forced local repo wihtout clearing the cache, the resolve output still shows resolving from that repository).
I am not using "SNAPSHOT" version, but I do often overwrite artifacts. I'm trying to build a more incremental system and this flag is the key to success, perhaps clarifying the documentation around this flag and what affects it, can help some of us understand what is going on. Since the hasChanged function is only comparing lists of mrids, I am not exactly sure if this flag would understand "changing" artifacts at all, since the revisions/modules wouldn't change but the artifacts themselves may.
There is also the transitivity issue with this flag.
SEE: IVY-1370)
> Problem with resolve (ivy.deps.changed) and timestamp of ivy.xml of dependencies
> --------------------------------------------------------------------------------
>
> Key: IVY-1176
> URL: https://issues.apache.org/jira/browse/IVY-1176
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.0
> Reporter: subes
> Priority: Blocker
>
> Hi,
> I am having the same Issue as Jan Vissers on the mailing list:
> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200803.mbox/%3C10985.145.53.56.90.1204817182.squirrel@webmail.xs4all.nl%3E
> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200803.mbox/%3C47D11E2A.1050704@cumquat.nl%3E
> The problem is, ivy.deps.changed does not get set to true if the timestamp of the dependencies ivy.xml got updated.
> The call to resolve actually tells me that the new files got downloaded (because of the updated timestamp), but ivy.deps.changed tells me that the artifacts did not change.
> [ivy:resolve] ---------------------------------------------------------------------
> [ivy:resolve] | | modules || artifacts |
> [ivy:resolve] | conf | number| search|dwnlded|evicted|| number|dwnlded|
> [ivy:resolve] ---------------------------------------------------------------------
> [ivy:resolve] | default | 26 | 1 | 1 | 0 || 26 | 1 |
> [ivy:resolve] | tests | 3 | 1 | 1 | 0 || 3 | 1 |
> [ivy:resolve] | sources | 10 | 1 | 1 | 0 || 10 | 1 |
> [ivy:resolve] ---------------------------------------------------------------------
> --> ivy.deps.changed is "false"
> This behaviour makes ivy.deps.changed mostly useless for me to implement a lazy build mechanism in a multi module project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira