path of least resistance is to grab the git cert and use curl to test e.g. 
>curl -help | grep certificate
 -E/--cert <cert[:passwd]> Client certificate file and password (SSL)
then automate in a bash script
I dont have a cert to when I try  
https://github.com/basis-technology-corp/find-jug-dist-dir-maven-plugini see 
the cat in front of a speeder Martin 
______________________________________________ 
Note de déni et de confidentialitéCe message est confidentiel et peut être 
privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec 
bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non 
autorisée ou la copie de ceci est interdite. Ce message sert à l'information 
seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant 
donné que les email peuvent facilement être sujets à la manipulation, nous ne 
pouvons accepter aucune responsabilité pour le contenu fourni.

 > Date: Fri, 8 Mar 2013 07:58:03 -0500
> Subject: Re: Release:perform failing on git ...
> From: [email protected]
> To: [email protected]
> 
> Mirko,
> 
> Thanks. I got around this for the moment by temporarily adding an
> IdentityFile line to my ~/.ssh/config. However, I'd rather be able to
> configure this in Maven somehow. I guess I have a JIRA in my future.
> 
> --benson
> 
> On Fri, Mar 8, 2013 at 12:51 AM, Mirko Friedenhagen
> <[email protected]> wrote:
> > Hello Benson,
> >
> > when this repository is on a host of it's own adding an entry to ssh-config
> > may help (http://linux.die.net/man/5/ssh_config) .
> >
> > Regards Mirko
> > --
> > Sent from my mobile
> > On Mar 8, 2013 2:53 AM, "Benson Margulies" <[email protected]> wrote:
> >
> >> Actually, I know what's happening.
> >>
> >> To talk to this repo, I need to use a custom ssh key.
> >>
> >> At command level, I use a shell script:
> >>
> >> git clone --config ssh.key=/users/benson/.ssh/id_basis_rsa "$@"
> >>
> >> THe question is, how do I get the m-r-p to do this?
> >>
> >>
> >> On Thu, Mar 7, 2013 at 8:49 PM, Tim Wu T <[email protected]> wrote:
> >>
> >> > I think it should better for you to provide more stacktrace.
> >> >
> >> > [ERROR] The git-clone command failed. This message is too limited to find
> >> > the root cause.
> >> >
> >> > Br,
> >> > Tim
> >> > -----Original Message-----
> >> > From: Benson Margulies [mailto:[email protected]]
> >> > Sent: Friday, March 08, 2013 9:47 AM
> >> > To: Maven Users List
> >> > Subject: Release:perform failing on git ...
> >> >
> >> > release plugin 2.3.2
> >> >
> >> > prepare does fine.
> >> >
> >> > perform fails with:
> >> >
> >> > [INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
> >> > find-jug-dist-dir-maven-plugin ---
> >> > [INFO] Checking out the project to perform the release ...
> >> > [INFO] Executing: /bin/sh -c cd
> >> > /Users/benson/x/find-jug-dist-dir-maven-plugin/target && git clone
> >> --branch
> >> > find-jug-dist-dir-maven-plugin-1
> >> > [email protected]:basis-technology-corp/find-jug-dist-dir-maven-plugin.git
> >> > /Users/benson/x/find-jug-dist-dir-maven-plugin/target/checkout
> >> > [INFO] Working directory:
> >> > /Users/benson/x/find-jug-dist-dir-maven-plugin/target
> >> > [ERROR] The git-clone command failed.
> >> >
> >> > scm looks like:
> >> >
> >> >     <scm>
> >> >       <connection>scm:git:[email protected]:
> >> > basis-technology-corp/find-jug-dist-dir-maven-plugin.git</connection>
> >> >       <developerConnection>scm:git:[email protected]:
> >> >
> >> >
> >> basis-technology-corp/find-jug-dist-dir-maven-plugin.git</developerConnection>
> >> >       <url>
> >> > https://github.com/basis-technology-corp/find-jug-dist-dir-maven-plugin
> >> > </url>
> >> >       <tag>HEAD</tag>
> >> >     </scm>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [email protected]
> >> > For additional commands, e-mail: [email protected]
> >> >
> >> >
> >>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
                                          

Reply via email to