Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: 
 <113701757.1146516520983.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Mon, 1 May 2006 15:48:40 -0500 (CDT)
From: "Brian Bonner (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Commented: (SCM-192) Issuing an SCM Checkout from SVN
 results in Issuer Not trusted error message
In-Reply-To: 
 <73170725.1146506201019.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

    [ http://jira.codehaus.org/browse/SCM-192?page=comments#action_64508 ] 

Brian Bonner commented on SCM-192:
----------------------------------

Yes, when I responded with (p) on the svn checkout, maven worked fine.  I guess it's working as designed.  Thanks.

> Issuing an SCM Checkout from SVN results in Issuer Not trusted error message
> ----------------------------------------------------------------------------
>
>          Key: SCM-192
>          URL: http://jira.codehaus.org/browse/SCM-192
>      Project: Maven SCM
>         Type: Bug

>  Environment: jdk 1.5.0_06, winxp
>     Reporter: Brian Bonner
>     Priority: Minor

>
>
> This might be a user error.  I haven't done many checkouts with Maven2 from svn.  This was probably the first and it was over an SSL connection.
> I issued:
> mvn scm:checkout -DconnectionUrl=scm:svn:https://svn.codehaus.org/xfire/trunk/xfire -DcheckoutDirectory=xfire
> and I receive:
> C:\mvneclipse>mvn scm:checkout -DconnectionUrl=scm:svn:https://svn.codehaus.org/
> xfire/trunk/xfire -DcheckoutDirectory=xfire
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
> [INFO] -------------------------------------------------------------------------
> ---
> [INFO] Building Maven Default Project
> [INFO]    task-segment: [scm:checkout] (aggregator-style)
> [INFO] -------------------------------------------------------------------------
> ---
> [INFO] [scm:checkout]
> [INFO] Working directory: C:\mvneclipse
> [INFO] Working directory: C:\mvneclipse
> [INFO] Command line: svn --non-interactive checkout https://svn.codehaus.org/xfi
> re/trunk/xfire mvneclipse
> [INFO] Command line: svn --non-interactive checkout https://svn.codehaus.org/xfi
> re/trunk/xfire mvneclipse
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: PROPFIND request failed on '/xfire/trunk/xfire'
> svn: PROPFIND of '/xfire/trunk/xfire': Server certificate verification failed: i
> ssuer is not trusted (https://svn.codehaus.org)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Command failed.
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon May 01 13:47:44 EDT 2006
> [INFO] Final Memory: 2M/5M
> [INFO] ------------------------------------------------------------------------
> I tried a straight svn checkout with:
> svn checkout https://svn.codehaus.org/xfire/trunk/xfire
> and I got:
> C:\mvneclipse>svn checkout https://svn.codehaus.org/xfire/trunk/xfire xfire
> Error validating server certificate for 'https://svn.codehaus.org:443':
>  - The certificate is not issued by a trusted authority. Use the
>    fingerprint to validate the certificate manually!
> Certificate information:
>  - Hostname: *.codehaus.org
>  - Valid: from Apr  7 00:00:00 2006 GMT until May  6 23:59:59 2007 GMT
>  - Issuer: AddTrust External TTP Network, AddTrust AB, SE
>  - Fingerprint: c0:f8:80:52:0a:0e:69:84:25:d5:67:07:8a:8c:1e:77:b3:06:77:49
> (R)eject, accept (t)emporarily or accept (p)ermanently?
> I didn't know if there is a better way to present this error message to the user or give them an option of accepting the certificate -- perhaps not.
> Anyway, I did searching on the mailing lists, google, maven site and I couldn't find anything about this msg.
> Brian

-- 
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