Now that the default is true, it means that if someone specify a version latest.integration, ivy will first look if the ivy file can be found using the 'latest.integration' token. If it is false, ivy will directly list the revisions, and according to the latest strategy find the latest one.
The performance impact on file system resolver is minor (just one file.exist per latest.integration dependency). But might be bigger with http (or other) remote repository. The effect of changing the default value will be that the people that use repositories containing an explicit text 'latest.integration' in their pattern will have to adpat their settings. I'm not sure how many people use this kind of repository. And I'm not even sure if ivy has support to publish to this kind of repository. We should maybe poll the ivy user community (I'm not sure it would give any result, but we can try). Gilles 2008/8/26 Xavier Hanin <[EMAIL PROTECTED]>: > Hi, > > I've already suggested this a couple of times, I'd like to change the > default value of alwaysCheckExactRevision from true to false. IMO this is > almost never actually used, slightly degrades performance and sometimes lead > to annoying bugs like invalid URLs (which should be fixed now). So, anyone > against the idea of changing this default value? > > Xavier > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
