You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lecharny <el...@gmail.com> on 2005/12/14 11:41:24 UTC
Problem deploying jars
Hi all,
I had problem deploying jars lately. First, I thought it could be a ssh
key problem, as pointed out by Brett, and as I had regenerated my keys,
but no way.
I can perfectly scp a jar to cvs.apache.org:
/scp ldap-clients-0.9.4-SNAPSHOT.jar
elecharny@cvs.apache.org:/www/cvs.apache.org/repository/directory-asn1/jars
works well. (note: I will discuss this command line further)
But when I do a :
maven multiproject:deploy, I get this result :
jar:jar:
[jar] Building
jar: /home/elecharny/apacheds/directory3/directory/asn1/trunk/codec/target/asn1-codec-0.3.4-SNAPSHOT.jar
jar:deploy:
[echo] maven.repo.list is set - using artifact deploy mode
Will deploy to 1 repository(ies): apachecvs
Deploying to repository: apachecvs
Using private key: /home/elecharny/.ssh/id_dsa
com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Unknown Source)
at
org.apache.maven.deploy.deployers.GenericSshDeployer.init(GenericSshDeployer.java:181)
...
(60 totally useless lines)
...
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Failed to deploy to: apachecvs Reason: Cannot connect. Reason: Auth fail
BUILD FAILED
File...... /home/elecharny/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
Unable to obtain goal [multiproject:deploy-callback]
-- /home/elecharny/.maven/cache/maven-artifact-plugin-1.4.1/plugin.jelly:94:13: <artifact:artifact-deploy> Unable to deploy to any repositories
Total time: 8 seconds
Finished at: Wed Dec 14 11:30:08 CET 2005
I have a Auth Fail for a reason I can't explain. My build.properties
file looks like :
maven.username=elecharny
maven.remote.group=directory
# User must specify:
maven.repo.apachecvs.username=elecharny
# Repository to deploy snapshots
maven.repo.apachecvs=scp://cvs.apache.org
maven.repo.apachecvs.directory=/www/cvs.apache.org/repository
maven.repo.apachecvs.group=directory
maven.repo.apachecvs.privatekey=/home/elecharny/.ssh/id_dsa
I can perfectly connect myself to both people.apache.org and
cvs.apache.org without having to type my password.
I noted some strange things however :
- we are members of directory group while all other projects on
www/cvs.apache.org/repository belong to group apcvs. I don't think it
makes any difference, but we are alone doing that...
- The subdirectory /www/cvs.apache.org/repository/directory-clients/jars
and poms are owned by akarasulu (which is ok) but the directory group
does not have write access (which is not good). I think that alex has to
cleanup it if we want to deploy jars in it ;)
Note about the scp command line : as you can see, I try to copy
ldap-client jar in asn1 directory : this is a side effect of the second
strange thing I saw. I couldn't scp this jar in the correct location, so
I tried to put it elsewhere. Don't worry : I have cleaned it after the
scp ;)
Re: Problem deploying jars [2]
Posted by Emmanuel Lecharny <el...@gmail.com>.
After investigations with Ersin, we found that Maven deploy plugin does
not support dsa keys, but only rsa keys. The error message was not
really explicit ...
We still have the problem with access rights in clients directory !
On Wed, 2005-12-14 at 11:41 +0100, Emmanuel Lecharny wrote:
> Hi all,
>
> I had problem deploying jars lately. First, I thought it could be a ssh
> key problem, as pointed out by Brett, and as I had regenerated my keys,
> but no way.
>
> I can perfectly scp a jar to cvs.apache.org:
>
> /scp ldap-clients-0.9.4-SNAPSHOT.jar
> elecharny@cvs.apache.org:/www/cvs.apache.org/repository/directory-asn1/jars
>
> works well. (note: I will discuss this command line further)
>
> But when I do a :
> maven multiproject:deploy, I get this result :
>
> jar:jar:
> [jar] Building
> jar: /home/elecharny/apacheds/directory3/directory/asn1/trunk/codec/target/asn1-codec-0.3.4-SNAPSHOT.jar
>
> jar:deploy:
> [echo] maven.repo.list is set - using artifact deploy mode
> Will deploy to 1 repository(ies): apachecvs
> Deploying to repository: apachecvs
> Using private key: /home/elecharny/.ssh/id_dsa
> com.jcraft.jsch.JSchException: Auth fail
> at com.jcraft.jsch.Session.connect(Unknown Source)
> at
> org.apache.maven.deploy.deployers.GenericSshDeployer.init(GenericSshDeployer.java:181)
> ...
> (60 totally useless lines)
> ...
> at com.werken.forehead.Forehead.run(Forehead.java:551)
> at com.werken.forehead.Forehead.main(Forehead.java:581)
> Failed to deploy to: apachecvs Reason: Cannot connect. Reason: Auth fail
>
> BUILD FAILED
> File...... /home/elecharny/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
> Element... maven:reactor
> Line...... 217
> Column.... 9
> Unable to obtain goal [multiproject:deploy-callback]
> -- /home/elecharny/.maven/cache/maven-artifact-plugin-1.4.1/plugin.jelly:94:13: <artifact:artifact-deploy> Unable to deploy to any repositories
> Total time: 8 seconds
> Finished at: Wed Dec 14 11:30:08 CET 2005
>
>
> I have a Auth Fail for a reason I can't explain. My build.properties
> file looks like :
>
> maven.username=elecharny
> maven.remote.group=directory
> # User must specify:
> maven.repo.apachecvs.username=elecharny
> # Repository to deploy snapshots
> maven.repo.apachecvs=scp://cvs.apache.org
> maven.repo.apachecvs.directory=/www/cvs.apache.org/repository
> maven.repo.apachecvs.group=directory
> maven.repo.apachecvs.privatekey=/home/elecharny/.ssh/id_dsa
>
> I can perfectly connect myself to both people.apache.org and
> cvs.apache.org without having to type my password.
>
> I noted some strange things however :
> - we are members of directory group while all other projects on
> www/cvs.apache.org/repository belong to group apcvs. I don't think it
> makes any difference, but we are alone doing that...
> - The subdirectory /www/cvs.apache.org/repository/directory-clients/jars
> and poms are owned by akarasulu (which is ok) but the directory group
> does not have write access (which is not good). I think that alex has to
> cleanup it if we want to deploy jars in it ;)
>
> Note about the scp command line : as you can see, I try to copy
> ldap-client jar in asn1 directory : this is a side effect of the second
> strange thing I saw. I couldn't scp this jar in the correct location, so
> I tried to put it elsewhere. Don't worry : I have cleaned it after the
> scp ;)
>
>
>
>
> ---------------------------------------------------------------------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
--
Emmanuel Lécharny
www.iktek.com