Craig, I don't know if you ever got to the bottom of this, but I had been having a similar problem. In my case, it seems that jar:deploy in Maven 1.0 silently failed to overwrite jar files that had been previously deployed using RC3. I don't know why this should be, and haven't time to try to find out. However, removing the old snapshot jars and allowing maven to deploy to a clean repository does seem to have fixed the problem.
John ===================================== John Taylor Astrogrid Java Developer Royal Observatory of Edinburgh http://www.roe.ac.uk/ifa/about/directory.html ===================================== ----- Original Message ----- From: "Craig S.Cottingham" < > To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Friday, July 16, 2004 9:05 PM Subject: jar:deploy* over scpexe failing inexplicably > When I run jar:deploy or jar:deploy-snapshot, Maven does not report an > error, but the jarfile is not deployed. When I run maven with the -X > flag, I see error messages: > > ===== > > Deploying: > /home/craigc/myjar/target/myjar-2.0-dev.jar-->mygroup/jars/myjar > -20040716.174447.jar > Executing command: ssh [EMAIL PROTECTED](my_employer).com mkdir -p > /home/maven/mygroup/jars > > Executing command: scp /home/craigc/myjar/target/myjar-2.0-dev.jar > [EMAIL PROTECTED](my_employer).com:/home/maven/mygroup/jars/myjar > -20040716.174447.jar > ERROR>scp: /home/maven/mygroup/jars/myjar-20040716.174447.jar: No such > file or directory > Executing command: ssh [EMAIL PROTECTED](my_employer).com chgrp maven > /home/maven/mygroup/jars/myjar-20040716.174447.jar > > Deploying: > /home/craigc/myjar/target/myjar-2.0-dev.jar.md5-->mygroup/jars/myjar > -20040716.174447.jar.md5 > Executing command: ssh [EMAIL PROTECTED](my_employer).com mkdir -p > /home/maven/mygroup/jars > > Executing command: scp > /home/craigc/myjar/target/frameworx-2.0-dev.jar.md5 > [EMAIL PROTECTED](my_employer).com:/home/maven/mygroup/jars/myjar > -20040716.174447.jar.md5 > ERROR>scp: /home/maven/mygroup/jars/myjar-20040716.174447.jar.md5: No > such file or directory > Executing command: ssh [EMAIL PROTECTED](my_employer).com chgrp maven > /home/maven/mygroup/jars/myjar-20040716.174447.jar.md5 > > Deploying: > /home/craigc/myjar/target/myjar-jar-snapshot-version-->mygroup/jars/ > myjar-snapshot-version > Executing command: ssh [EMAIL PROTECTED](my_employer).com mkdir -p > /home/maven/mygroup/jars > > Executing command: scp > /home/craigc/myjar/target/myjar-jar-snapshot-version > [EMAIL PROTECTED](my_employer).com:/home/maven/mygroup/jars/myjar- > snapshot-version > ERROR>scp: /home/maven/mygroup/jars/myjar-snapshot-version: No such > file or directory > Executing command: ssh [EMAIL PROTECTED](my_employer).com chgrp maven > /home/maven/mygroup/jars/myjar-snapshot-version > > ===== > > (Edited to remove what my employer might consider sensitive details, so > typos may be mine.) Now for the oddities: > > * myjar-2.0-dev.jar exists in target/, but myjar-2.0-dev.jar.md5 and > myjar-jar-snapshot-version do not. > * If I manually type in the first scp command line (for > myjar-2.0-dev.jar), the file is copied. > > Here's the relevant portion of project.properties: > > ===== > > maven.repo.central=server1.(my_employer).com > maven.repo.central.directory=/home/maven > maven.repo.remote=http://www.(my_employer).com/maven/,http:// > www.ibiblio.org/maven/,http://maven-plugins.sf.net/maven/ > maven.repo.list=server1 > maven.repo.server1=scpexe://server1.(my_employer).com > maven.repo.server1.directory=/home/maven > maven.repo.server1.group=maven > maven.repo.server1.compress=false > > ===== > > And the relevant portion of ~/build.properties: > > ===== > > maven.repo.server1.username=craigc > maven.repo.server1.privatekey=/home/craigc/.ssh/id_dsa > > ===== > > It gets odder. If I change "scpexe" to "scp", it works as it's supposed > to. Trying to execute jar:deploy-snapshot using the same files on the > machine that holds the repository (server1), "scp" *doesn't* work, but > "scpexe" does. > > The JVMs are the same, but the versions of ssh/OpenSSL are different: > > [EMAIL PROTECTED]:~/myjar$ java -version > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) > [EMAIL PROTECTED]:~/myjar$ ssh -V > OpenSSH_3.8.1p1 Debian 1:3.8.1p1-4, OpenSSL 0.9.7d 17 Mar 2004 > > [EMAIL PROTECTED]:~/myjar$ java -version > java version "1.4.2_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) > [EMAIL PROTECTED]:~/myjar$ ssh -V > OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.6b [engine] 9 Jul > 2001 > > I suppose that might account for why "scpexe" works on one box but not > the other, but I still can't understand why entering the failed command > by hand succeeds. I also can't account for why "scp" fails on one box > but not the other. > > Is there anything I can do to get more diagnostics out of Maven? Since > I've found a workaround, this isn't a showstopper, but the > inconsistency of behavior suggests that this might cause problems down > the road. > > Thanks in advance for any advice that's offered. > > -- > Craig S. Cottingham > [EMAIL PROTECTED] > OpenPGP key available from: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C > > > --------------------------------------------------------------------- > 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]
