[ https://issues.apache.org/jira/browse/IVY-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188300#comment-13188300 ]
Glenn J. Mason commented on IVY-1176: ------------------------------------- I've just hit this exact issue when trying to avoid certain steps in my build using <uptodate>. Specifically: 1) publish a new SNAPSHOT upstream - the timestamp is updated in the repository (but the revision stays the same) 2) resolve for a downstream module - new SNAPSHOT is downloaded but ivy.deps.changed=false I wanted to use this for those odd cases where the upstream change means the downstream module needs recompilation, but without change in the module itself - I was hoping to avoid <javac>ing everything every time (although I think it avoids recompiling if it doesn't have to?). Any reason ivy.deps.changed doesn't consider the timestamp? > 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.squir...@webmail.xs4all.nl%3E > http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200803.mbox/%3c47d11e2a.1050...@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