Quoting Xavier Hanin <[EMAIL PROTECTED]>:
Since Ivy does not mandate anything about revision names, it always check the exact revision you ask before evaluating it as a constraint. Fortunately you can disable that, using alwaysCheckExactRevision="false" on your resolver. I wonder if it wouldn't be interesting to change the default value of this attribute in 2.0, since I think that very few people actually benefit from it. WDYT?
If true leads ivy to checking every [revision] value even though it may be in fact a range and can't possibly corresponds to an actual pom, yes, I would agree that it isn't really beneficial being the default.
Thanks. -- Jing
