Description
When m2compatible mode is turned on, Ivy re-arranges the org id so that the repo is searched in a hierarchical version of that org id, in Maven 2 style. So
"org.this.that.there"
becomes
org/this/that/there
However, on a failed resolution of the artifact in some repo, the repository search/match paths that Ivy is trying to search/match do not reflect the organization in this hierarchical format, but rather in the original dotted format.
So the display of the remote web site path, file path, etc. that Ivy is looking at for the artifact is actually wrong.
Note that this bug was discovered by me a couple of months ago, and I forgot to report it. I have not verified that it still happens in the current 1.4RC1, and regret that I do not have time to do so in the next few days, but I presume that if somebody else has not reported it, it is still there.
Regards,