Ok, I have a better understanding now that I've seen your properties. Seems this is a bug introduced in the latest version. I will work on a fix immediately. I will verify the other bug you originally reported doesn't exist either.
You can also rollback using plugin:download -Dversion=1.4.1 with the rest of the parameters the same to get back to the last working version. Also, you can use: maven.repo.profilium.scp.executable=c:/path/to/plink instead of renaming an executable on the path. Cheers, Brett On 6/10/05, Jean-Luc Wasmer <[EMAIL PROTECTED]> wrote: > Jean-Luc Wasmer wrote: > > > Brett, > > > > Please ignore my last e-mail: I finally found how to upgrade plugins > > (thanks to the pdf file). > > looks like it didn't make it to the mailing list's server.... > > Anyways, I figured out how to upgrade the plugins and did so for all of > them (as described in http://maven.apache.org/start/download.html). > > Now, I have something weird: a connection error that never happened in > the past: > > Failed to deploy to: profilium Reason: > org.apache.maven.wagon.authentication.AuthenticationException: Private > key was not found. You must define a private key or a password for repo: > profilium > > Here is the content of my build.properties file: > > maven.username = jlwasmer > maven.repo.list=profilium > maven.repo.profilium=scpexe://maven.profilium.lan > maven.repo.profilium.directory=/home/htdocs/maven > maven.repo.profilium.username=jlwasmer > maven.repo.profilium.group=maven > > I use putty's ssh program (plink.exe) that I renamed ssh.exe. The key is > stored by their ssh-agent program so when I do: > ssh [EMAIL PROTECTED] > in a command prompt, it connects right away and I don't have to enter a > password. > I do the same thing for scp. > > Once again, that setup used to work. > > JL > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
