You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Brendan Sibre <br...@sibre.net> on 2009/12/10 21:49:51 UTC
401 error with Maven Release Plugin
A previous poster wrote:
>
>Thanks for your response, this fixed the problem! However, another issue
comes up - *release*:*perform* almost worked out except at the very end it
failed to upload the artifact >to the repo, and the error is
>
>[INFO] [INFO] Error deploying artifact: Failed to transfer file: ......
Return code is: *401*
>
>I believe this is a permission related issue. But I've got the correct
server username/password pairs in settings.xml and running the deploy goal
in the lifecycle has no problem >having the artifact deployed, it's just the
*release*:*perform* that gets stuck with the permission problem. Anyone
knows why this happens please?
This is with an https url and, like the previous poster, I can do a maven
deploy without any issues.
Anyone have any ideas?
Re: 401 error with Maven Release Plugin
Posted by Matt Milliss <ma...@gmail.com>.
We had the same problem with Archiva but it was fixed with the latest
upgrade, which is why I asked. Sorry don't think I can help.
Cheers
Matt
On 11/12/2009 10:47 AM, Brendan Sibre wrote:
> Actually, using Artifactory 2.1.0. And it is configured to mirror
> everything.
>
> So far I'm guessing that it's one of two problems:
> 1) I don't have things mapped properly between my ~/.m2/settings.xml
> and $MAVEN_HOME/conf/settings.xml where the shared configuration
> defines the distributionManagement and my settings defines server
> credentials.
> 2) I have some very vague recollection of there being a problem with
> Maven passing the MAVEN_HOME value to the forked maven when MAVEN_HOME
> points to a symlink. Although I've tried changing MAVEN_HOME to the
> actual directory as well as passing in the -DmavenHome parameter.
>
> On Thu, Dec 10, 2009 at 5:20 PM, Matt Milliss <matt.milliss@gmail.com
> <ma...@gmail.com>> wrote:
>
> are you using Archiva as your repo?
>
>
> On 11/12/2009 7:49 AM, Brendan Sibre wrote:
>
> A previous poster wrote:
>
> Thanks for your response, this fixed the problem! However,
> another issue
>
> comes up - *release*:*perform* almost worked out except at the
> very end it
> failed to upload the artifact>to the repo, and the error is
>
> [INFO] [INFO] Error deploying artifact: Failed to transfer
> file: ......
>
> Return code is: *401*
>
> I believe this is a permission related issue. But I've got
> the correct
>
> server username/password pairs in settings.xml and running the
> deploy goal
> in the lifecycle has no problem>having the artifact deployed,
> it's just the
> *release*:*perform* that gets stuck with the permission
> problem. Anyone
> knows why this happens please?
> This is with an https url and, like the previous poster, I can
> do a maven
> deploy without any issues.
>
> Anyone have any ideas?
>
>
>
Re: 401 error with Maven Release Plugin
Posted by Brendan Sibre <br...@sibre.net>.
Actually, using Artifactory 2.1.0. And it is configured to mirror
everything.
So far I'm guessing that it's one of two problems:
1) I don't have things mapped properly between my ~/.m2/settings.xml and
$MAVEN_HOME/conf/settings.xml where the shared configuration defines the
distributionManagement and my settings defines server credentials.
2) I have some very vague recollection of there being a problem with Maven
passing the MAVEN_HOME value to the forked maven when MAVEN_HOME points to a
symlink. Although I've tried changing MAVEN_HOME to the actual directory as
well as passing in the -DmavenHome parameter.
On Thu, Dec 10, 2009 at 5:20 PM, Matt Milliss <ma...@gmail.com>wrote:
> are you using Archiva as your repo?
>
>
> On 11/12/2009 7:49 AM, Brendan Sibre wrote:
>
>> A previous poster wrote:
>>
>>
>>> Thanks for your response, this fixed the problem! However, another issue
>>>
>>>
>> comes up - *release*:*perform* almost worked out except at the very end it
>> failed to upload the artifact>to the repo, and the error is
>>
>>
>>> [INFO] [INFO] Error deploying artifact: Failed to transfer file: ......
>>>
>>>
>> Return code is: *401*
>>
>>
>>> I believe this is a permission related issue. But I've got the correct
>>>
>>>
>> server username/password pairs in settings.xml and running the deploy goal
>> in the lifecycle has no problem>having the artifact deployed, it's just
>> the
>> *release*:*perform* that gets stuck with the permission problem. Anyone
>> knows why this happens please?
>> This is with an https url and, like the previous poster, I can do a maven
>> deploy without any issues.
>>
>> Anyone have any ideas?
>>
>>
>>
>
Re: 401 error with Maven Release Plugin
Posted by Matt Milliss <ma...@gmail.com>.
are you using Archiva as your repo?
On 11/12/2009 7:49 AM, Brendan Sibre wrote:
> A previous poster wrote:
>
>> Thanks for your response, this fixed the problem! However, another issue
>>
> comes up - *release*:*perform* almost worked out except at the very end it
> failed to upload the artifact>to the repo, and the error is
>
>> [INFO] [INFO] Error deploying artifact: Failed to transfer file: ......
>>
> Return code is: *401*
>
>> I believe this is a permission related issue. But I've got the correct
>>
> server username/password pairs in settings.xml and running the deploy goal
> in the lifecycle has no problem>having the artifact deployed, it's just the
> *release*:*perform* that gets stuck with the permission problem. Anyone
> knows why this happens please?
> This is with an https url and, like the previous poster, I can do a maven
> deploy without any issues.
>
> Anyone have any ideas?
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: 401 error with Maven Release Plugin
Posted by Brendan Sibre <bt...@gmail.com>.
This is Maven 2.2.1 with release plugin 2.0-beta-8.
On Fri, Dec 11, 2009 at 2:26 AM, Anders Hammar <an...@hammar.net> wrote:
> You've tried different version of Maven? 2.2.1? 3.0-alpha-5?
>
> /Anders
>
> On Thu, Dec 10, 2009 at 21:49, Brendan Sibre <br...@sibre.net> wrote:
>
> > A previous poster wrote:
> > >
> > >Thanks for your response, this fixed the problem! However, another issue
> > comes up - *release*:*perform* almost worked out except at the very end
> it
> > failed to upload the artifact >to the repo, and the error is
> > >
> > >[INFO] [INFO] Error deploying artifact: Failed to transfer file: ......
> > Return code is: *401*
> > >
> > >I believe this is a permission related issue. But I've got the correct
> > server username/password pairs in settings.xml and running the deploy
> goal
> > in the lifecycle has no problem >having the artifact deployed, it's just
> > the
> > *release*:*perform* that gets stuck with the permission problem. Anyone
> > knows why this happens please?
> > This is with an https url and, like the previous poster, I can do a maven
> > deploy without any issues.
> >
> > Anyone have any ideas?
> >
>
Re: 401 error with Maven Release Plugin
Posted by Anders Hammar <an...@hammar.net>.
You've tried different version of Maven? 2.2.1? 3.0-alpha-5?
/Anders
On Thu, Dec 10, 2009 at 21:49, Brendan Sibre <br...@sibre.net> wrote:
> A previous poster wrote:
> >
> >Thanks for your response, this fixed the problem! However, another issue
> comes up - *release*:*perform* almost worked out except at the very end it
> failed to upload the artifact >to the repo, and the error is
> >
> >[INFO] [INFO] Error deploying artifact: Failed to transfer file: ......
> Return code is: *401*
> >
> >I believe this is a permission related issue. But I've got the correct
> server username/password pairs in settings.xml and running the deploy goal
> in the lifecycle has no problem >having the artifact deployed, it's just
> the
> *release*:*perform* that gets stuck with the permission problem. Anyone
> knows why this happens please?
> This is with an https url and, like the previous poster, I can do a maven
> deploy without any issues.
>
> Anyone have any ideas?
>