ns accepter aucune responsabilité pour le contenu fourni.
> Date: Fri, 8 Mar 2013 07:58:03 -0500
> Subject: Re: Release:perform failing on git ...
> From: bimargul...@gmail.com
> To: users@maven.apache.org
>
> Mirko,
>
> Thanks. I got around this for the moment by temp
t; > the root cause.
>> >
>> > Br,
>> > Tim
>> > -Original Message-
>> > From: Benson Margulies [mailto:bimargul...@gmail.com]
>> > Sent: Friday, March 08, 2013 9:47 AM
>> > To: Maven Users List
>> > Subject: Release:perfor
gt; From: Benson Margulies [mailto:bimargul...@gmail.com]
> > 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 fa
: Release:perform failing on git ...
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,
om]
> 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
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
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/t
