[
https://issues.apache.org/jira/browse/MINDEXER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965381#comment-17965381
]
Olivier Lamy commented on MINDEXER-239:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#655|https://github.com/apache/maven-indexer/issues/655].
> Better error messaging
> ----------------------
>
> Key: MINDEXER-239
> URL: https://issues.apache.org/jira/browse/MINDEXER-239
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 7.1.5
>
>
> When for example SMO get "unexpected" response, stack looks like this:
> {noformat}
> Caused by: java.io.IOException: Unexpected response:
> org.apache.maven.search.api.transport.Java11HttpClientTransport$ResponseImpl@6e4c0d8c
> at
> org.apache.maven.search.backend.smo.internal.SmoSearchBackendImpl.fetch
> (SmoSearchBackendImpl.java:146)
> at
> org.apache.maven.search.backend.smo.internal.SmoSearchBackendImpl.search
> (SmoSearchBackendImpl.java:121)
> at
> org.apache.maven.search.backend.smo.internal.SmoSearchBackendImpl.search
> (SmoSearchBackendImpl.java:53)
> {noformat}
> It would be nice to know what WAS that unexpected response (at least HTTP
> response code and phrase?)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
