You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Steve Molloy <sm...@convera.com> on 2006/08/09 14:23:32 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Arnaud HERITIER <ah...@gmail.com>.
Ok,
I'll close this issue and I'll add a note on the m1 homepage.
http://people.apache.org/~aheritier/m1-stage-site/maven-1.x/
We'll release this new version ASAP
Arnaud
On 8/11/06, Siegfried Goeschl <si...@it20one.at> wrote:
>
> Hi Arnaud,
>
> works like a charm now .... :-)
>
> Cheers,
>
> Siegfried Goeschl
>
> Arnaud HERITIER wrote:
> > I just deployed the SNAPSHOT of the version 1.8.1. You can test it with
> > maven 1.1 beta 3
> >
> > maven plugin:download -DgroupId=maven
> > -DartifactId=*maven-artifact-plugin* -Dversion=*1.8.1*-SNAPSHOT
> > -Dmaven.repo.remote=http://www.ibiblio.org/maven,
> http://people.apache.org/repo/m1-snapshot-repository/
> >
> >
> > It should fix the problem.
> > When I upgraded wagon dependencies I changed a little bit the plugin's
> code
> > to not have this error of RejectedKey.
> > The problem Is that in the beta 3 we upgraded these dependencies
> (through
> > the core) but we don't bundle the new artifact plugin :-(
> > It's my fault.
> >
> > Cheers.
> >
> > Arnaud
> >
> > On 8/10/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
> >
> >>
> >> This too is exactly the info we need in the defect entry! Your
> >> perspective in
> >> the issue, including what doesn't work and what does work, is
> >> important to
> >> eventual resolution.
> >>
> >> Would you mind adding your notes to the issue - what works and does not
> >> work?
> >>
> >>
> >> Quoting Steve Molloy <sm...@convera.com>:
> >>
> >> > 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.1b3to
> >> this
> >> > > JIRA, please?
> >> > > http://jira.codehaus.org/browse/MPARTIFACT-71
> >> > >
> >> > >
> >> > > > On 8/9/06, Steve Molloy <sm...@convera.com> 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:smolloy@convera.com]
> >> > > > > > 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: users-unsubscribe@maven.apache.org
> >> > > For additional commands, e-mail: users-help@maven.apache.org
> >> > >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Arnaud,
works like a charm now .... :-)
Cheers,
Siegfried Goeschl
Arnaud HERITIER wrote:
> I just deployed the SNAPSHOT of the version 1.8.1. You can test it with
> maven 1.1 beta 3
>
> maven plugin:download -DgroupId=maven
> -DartifactId=*maven-artifact-plugin* -Dversion=*1.8.1*-SNAPSHOT
> -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
>
>
> It should fix the problem.
> When I upgraded wagon dependencies I changed a little bit the plugin's code
> to not have this error of RejectedKey.
> The problem Is that in the beta 3 we upgraded these dependencies (through
> the core) but we don't bundle the new artifact plugin :-(
> It's my fault.
>
> Cheers.
>
> Arnaud
>
> On 8/10/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
>
>>
>> This too is exactly the info we need in the defect entry! Your
>> perspective in
>> the issue, including what doesn't work and what does work, is
>> important to
>> eventual resolution.
>>
>> Would you mind adding your notes to the issue - what works and does not
>> work?
>>
>>
>> Quoting Steve Molloy <sm...@convera.com>:
>>
>> > 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 <sm...@convera.com> 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:smolloy@convera.com]
>> > > > > > 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: users-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Arnaud HERITIER <ah...@gmail.com>.
I just deployed the SNAPSHOT of the version 1.8.1. You can test it with
maven 1.1 beta 3
maven plugin:download -DgroupId=maven
-DartifactId=*maven-artifact-plugin* -Dversion=*1.8.1*-SNAPSHOT
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
It should fix the problem.
When I upgraded wagon dependencies I changed a little bit the plugin's code
to not have this error of RejectedKey.
The problem Is that in the beta 3 we upgraded these dependencies (through
the core) but we don't bundle the new artifact plugin :-(
It's my fault.
Cheers.
Arnaud
On 8/10/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
>
> This too is exactly the info we need in the defect entry! Your
> perspective in
> the issue, including what doesn't work and what does work, is important to
> eventual resolution.
>
> Would you mind adding your notes to the issue - what works and does not
> work?
>
>
> Quoting Steve Molloy <sm...@convera.com>:
>
> > 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 <sm...@convera.com> 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:smolloy@convera.com]
> > > > > > 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Jeff Jensen <je...@upstairstechnology.com>.
This too is exactly the info we need in the defect entry! Your perspective in
the issue, including what doesn't work and what does work, is important to
eventual resolution.
Would you mind adding your notes to the issue - what works and does not work?
Quoting Steve Molloy <sm...@convera.com>:
> 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 <sm...@convera.com> 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:smolloy@convera.com]
> > > > > 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Steve Molloy <sm...@convera.com>.
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 <sm...@convera.com> 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:smolloy@convera.com]
> > > > 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Jeff Jensen <je...@upstairstechnology.com>.
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 <sm...@convera.com> 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:smolloy@convera.com]
> > > 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Steve Molloy <sm...@convera.com>.
Sure, just tried it, but the build failed with a ClassNotFoundException
for AbstractSshWagon... One thing weird is that the tar and the md5
don't have the same dates (July 18th vs August 1st...). It was in
20060630 right? (used
http://people.apache.org/~aheritier/maven/1.X/snapshots/20060630/maven-1.1-beta-3-SNAPSHOT.tar.bz2 ).
Steve
Stacktrace:
BUILD FAILED
File......
file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly
Element... artifact:artifact-deploy
Line...... 103
Column.... 9
org/apache/maven/wagon/providers/ssh/AbstractSshWagon
org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal
[jar:deploy] --
file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly:103:9: <artifact:artifact-deploy> org/apache/maven/wagon/providers/ssh/AbstractSshWagon
at org.apache.maven.werkz.Goal.fire(Goal.java:663)
at org.apache.maven.werkz.Goal.attain(Goal.java:592)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:535)
at org.apache.maven.cli.App.main(App.java:1318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
org.apache.commons.jelly.JellyTagException:
file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly:103:9: <artifact:artifact-deploy> org/apache/maven/wagon/providers/ssh/AbstractSshWagon
at
org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:193)
at
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79)
at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
at org.apache.maven.jelly.tags.werkz.MavenGoalTag
$MavenGoalAction.performAction(MavenGoalTag.java:109)
at org.apache.maven.werkz.Goal.fire(Goal.java:656)
at org.apache.maven.werkz.Goal.attain(Goal.java:592)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:535)
at org.apache.maven.cli.App.main(App.java:1318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/wagon/providers/ssh/AbstractSshWagon
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:316) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:119)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:90)
at
org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180)
... 19 more
Root cause
java.lang.NoClassDefFoundError:
org/apache/maven/wagon/providers/ssh/AbstractSshWagon
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:316) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:119)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:90)
at
org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180)
at
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79)
at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
at org.apache.maven.jelly.tags.werkz.MavenGoalTag
$MavenGoalAction.performAction(MavenGoalTag.java:109)
at org.apache.maven.werkz.Goal.fire(Goal.java:656)
at org.apache.maven.werkz.Goal.attain(Goal.java:592)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:535)
at org.apache.maven.cli.App.main(App.java:1318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Root cause
java.lang.NoClassDefFoundError:
org/apache/maven/wagon/providers/ssh/AbstractSshWagon
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:316) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:119)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:90)
at
org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180)
at
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79)
at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
at org.apache.maven.jelly.tags.werkz.MavenGoalTag
$MavenGoalAction.performAction(MavenGoalTag.java:109)
at org.apache.maven.werkz.Goal.fire(Goal.java:656)
at org.apache.maven.werkz.Goal.attain(Goal.java:592)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:535)
at org.apache.maven.cli.App.main(App.java:1318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Final Memory : 7M/17M
Total time : 27 seconds
Finished at : Wednesday, August 9, 2006 10:11:22 EDT AM
On Wed, 2006-09-08 at 15:58 +0200, Arnaud HERITIER wrote:
> Steve,
>
> Even if you don't use this snapshot, can you test it to tell us if this
> one works also for you.
> We are searching what we changed since this snapshot and the official beta
> 3 to fix it in the RC1.
> We are trying to produce the RC1 at the end of the month.
> If the returns about it are good, we'll release the final 1.1 in september
> (probably in mid-september).
> It's why we need to have as many feedback as possible about this beta 3 to
> have less Release Candidates.
>
> Cheers
>
> Arnaud
>
> On 8/9/06, Steve Molloy <sm...@convera.com> 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:smolloy@convera.com]
> > > 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Arnaud HERITIER <ah...@gmail.com>.
Steve,
Even if you don't use this snapshot, can you test it to tell us if this
one works also for you.
We are searching what we changed since this snapshot and the official beta
3 to fix it in the RC1.
We are trying to produce the RC1 at the end of the month.
If the returns about it are good, we'll release the final 1.1 in september
(probably in mid-september).
It's why we need to have as many feedback as possible about this beta 3 to
have less Release Candidates.
Cheers
Arnaud
On 8/9/06, Steve Molloy <sm...@convera.com> 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:smolloy@convera.com]
> > 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Steve Molloy <sm...@convera.com>.
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:smolloy@convera.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven 1.1-beta3 & maven-artifact-plugin 1.8
Posted by Jeff Jensen <je...@upstairstechnology.com>.
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:smolloy@convera.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org