[
http://jira.codehaus.org/browse/MNG-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146383#action_146383
]
Andreas Krüger commented on MNG-3230:
-------------------------------------
Hello, Serge,
??This can be solved outside maven. Just add the self signed certificate to JVM
certificate keystore.??
May be (have not tried).
The issue that I would like to see solved inside Maven:
Give a detailed and sensible error message which clearly points to HTTPS and
the certificate
as the problem area.
> HTTPS with self-signed certificate does not work, no error message.
> -------------------------------------------------------------------
>
> Key: MNG-3230
> URL: http://jira.codehaus.org/browse/MNG-3230
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.7
> Reporter: Andreas Krüger
> Fix For: 2.0.x
>
>
> We have a repository server that serves the same files both via HTTPS and
> HTTP.
> Maven is not able to find artifacts when using HTTPS. All goes well when
> using HTTP.
> The problem probably is that the HTTPS - certificate used by the repository
> server is self-signed, and Maven has not been configured to accept that
> certificate as genuine. (This is a guess.)
> Expected behavior: With HTTPS, build does not continue. Maven gives an error
> message indicating the problem is certificate-related.
> Behavior seen: Maven reacts as if there were no problem connecting the
> repository, but as if the artifact were missing from the repository. It
> continues to search other repositories as happen to be configured. (However,
> the artifact is clearly there, e.g., can be downloaded with "wget
> --no-check-certificate " via HTTPS.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
