directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Problem deploying jars
Date Wed, 14 Dec 2005 10:41:24 GMT
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

/scp ldap-clients-0.9.4-SNAPSHOT.jar

works well. (note: I will discuss this command line further)

But when I do a :
maven multiproject:deploy, I get this result :

    [jar] Building
jar: /home/elecharny/apacheds/directory3/directory/asn1/trunk/codec/target/asn1-codec-0.3.4-SNAPSHOT.jar

    [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)
 (60 totally useless lines)
        at com.werken.forehead.Forehead.main(
Failed to deploy to: apachecvs Reason: Cannot connect. Reason: Auth fail

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
file looks like :

# User must specify:
# Repository to deploy snapshots

I can perfectly connect myself to both and without having to type my password.

I noted some strange things however :
- we are members of directory group while all other projects on
www/ belong to group apcvs. I don't think it
makes any difference, but we are alone doing that...
- The subdirectory /www/
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 ;)

View raw message