[
https://issues.apache.org/jira/browse/IVY-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-456.
------------------------------
Resolution: Fixed
I've added a junit test testing the message logs (developer note: you can use
the MockMessageImpl class when you need to test messages), and updated the
trace.
Now attempts are appended to the attempt list as soons as they occur, and
reported only in case of failure. So we now have attempts logs corresponding
exactly to what Ivy did, at last :-)
I've also improved these logs, to give more details when no revision matching a
pattern is found, and reviewed the layout of the messages to make them a little
more readable (but with long urls you will still have long lines...).
> Invalid error report with m2compatible resolver
> -----------------------------------------------
>
> Key: IVY-456
> URL: https://issues.apache.org/jira/browse/IVY-456
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 1.4.1
> Reporter: Xavier Hanin
> Assigned To: Xavier Hanin
> Fix For: 2.0
>
>
> Sometimes with m2compatible resolver when they do not find the asked
> revision, the error reported on the console at the end of the resolve do not
> match what it actually did. For instance here is a verbose snippet:
> {code}
> [ivy:resolve] CLIENT ERROR: Not Found
> url=http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/0.9.4/logback-classic-0.9.4.pom
> [ivy:resolve] CLIENT ERROR: Not Found
> url=http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/0.9.4/logback-classic-0.9.4.jar
> [ivy:resolve] maven2-http: no ivy file nor artifact found for [
> ch.qos.logback | logback-classic | 0.9.4 ]
> [ivy:resolve] tried
> http://repo1.maven.org/maven2/ch.qos.logback/logback-classic/0.9.4/logback-classic-0.9.4.pom
> [ivy:resolve] tried
> http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/0.9.4/logback-classic-0.9.4.jar
> {code}
> As you can see, the CLIENT ERROR reported by commons httpclient show that Ivy
> tried the good location, but then the message indicates that the attempt was
> done as if m2compatible was set to false. What is strange is that it works
> properly for artifacts.
> Here is the settings snippet leading to this problem:
> {code:xml}
> <ibiblio name="maven2-http" m2compatible="true"
> root="http://repo1.maven.org/maven2"; />
> {code}
> Note that this kind of problem also occurs for different reasons, when you
> alwayscheckExactRevision="false", for instance, I still report that it tried
> to access the resource with the dynamic revision.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
