[
https://jira.codehaus.org/browse/MNG-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337661#comment-337661
]
Sanne Grinovero commented on MNG-5238:
--------------------------------------
Hi all, I've been using {code}mvn deploy{code} from version 3.0.4 for many
months now without any problem - running various versions of Fedora in the
meantime (I upgrade to latest as soon as it gets out) and it always worked
fine, but now attempting to deploy the same software from the same Maven
version on an Ubuntu server, I'm getting this 301 error.
Any clue on why it should fail just changing operating system?
It's not a server configuration problem (running Nexus) as I can double check
from other systems (mainly other Fedora machines and some Macbooks running OSX)
and the same deploy process works fine.
> 301, ReasonPhrase:Moved Permanently
> -----------------------------------
>
> Key: MNG-5238
> URL: https://jira.codehaus.org/browse/MNG-5238
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Errors, Plugins and Lifecycle
> Affects Versions: 3.0.4
> Environment: Continuum 1.3.6, Archiva 1.1.2
> Reporter: Lionel Champalaune
>
> I was in Maven 2.0.9 until two weeks ago.
> I did integration test with maven 3.0.3 and everything was working fine.
> When I decided to migrate my integration system this week I upgrade to 3.0.4
> and then the clean deploy failed with this error:
> Could not transfer artifact groupe:artifact:pom:0.5.0-20120203.164640-2
> from/to snapshots (http://archiva.company.fr/repository/snapshots/): Failed
> to transfer file:
> http://archiva.company.fr/repository/snapshots/groupe/artifact/0.5.0-SNAPSHOT/panel-0.5.0-20120203.164640-2.pom.
> Return code is: 301, ReasonPhrase:Moved Permanently
> I don't know how to investigate the problem because it's working with 3.0.3
> (Wagon enhancement ?)
> I migrate to 3.0.3 but I think it's better to be with the last version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
