Well, I was about to... But when I reproduced it, I thought I'd dig a bit to see what might be wrong. I started by changing the NullKnownHostProvider by a FileKnownHostProvider which would validate my provider, then replaced the cached class files with the newly compiled ones. It worked fine... Then I reverted to NullKnownHostProvider, but it still worked fine!!!
So, to recap, installing maven-artifact-plugin 1.8 as-is fails with host rejected error. Replacing its class files with the locally compiled trunk version fixes my problem. What changed between 1.8 and trunk? Seems to be the right thing, at least for me... ;-) And is there a 1.9-SNAPSHOT available somewhere? Steve On Thu, 2006-10-08 at 08:01 -0500, Jeff Jensen wrote: > Hi Steve, > > Would you mind adding your details on the deploy error with m1.1b3 to this > JIRA, please? > http://jira.codehaus.org/browse/MPARTIFACT-71 > > > > On 8/9/06, Steve Molloy <[EMAIL PROTECTED]> wrote: > > > > > > Thanks, I guess I'll stick with 1.0.2 until the next release, hoping > > > this issue will be fixed. Is there any ETA set for the next 1.1 > > > release yet? > > > > > > Steve > > > > > > On Wed, 2006-09-08 at 08:23 -0500, Jeff Jensen wrote: > > > > Hi Steve, > > > > > > > > Yes, this is an issue I encountered as well. I have found that > > > > the 6/30 1.1-beta3-SNAPSHOT does not have this problem, but every > > > > release since > > > then > > > > does. > > > > See 20060630/ here: > > > > http://people.apache.org/~aheritier/maven/1.X/snapshots/ > > > > > > > > We are researching the problem to find a fix. > > > > > > > > In the meantime, I suggest the 6/30 snapshot if you would like to > > > > use > > > 1.1. > > > > It is very solid and the current one we use for our production > > > > work > > > (we've > > > > used nearly every one of those snapshots all along as they were > > > published). > > > > > > > > > > > > -----Original Message----- > > > > From: Steve Molloy [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, August 09, 2006 7:24 AM > > > > To: users@maven.apache.org > > > > Subject: Maven 1.1-beta3 & maven-artifact-plugin 1.8 > > > > > > > > Hi, > > > > > > > > I just upgraded from maven 1.0.2 to 1.1-beta3, and got the > > > > maven-artifact-plugin 1.8 along with it. But Now I can't deploy > > > > any artifacts because scp refuses my host key, while scpexe just > > > > doesn't do anything at all, but doesn't complain... > > > > > > > > So, I've reverted back to 1.0.2 for now, but are there any > > > > plans > > > for > > > > fixing these problems? (I'm running maven on JDK 1.5.0_07, on > > > > Fedora > > > core > > > > 5). > > > > > > > > Thanks, > > > > Steve > > > --------------------------------------------------------------------- > 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]
