[
https://jira.codehaus.org/browse/MNG-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292027#comment-292027
]
Lionel Champalaune commented on MNG-5238:
-----------------------------------------
There is nothing in archiva side.
It's a problem in the deploy phase of maven.
ERROR: Error deploying artifact: Failed to transfer file ....301...
As I said it's working in 3.0.3 but not in 3.0.4.
Sorry to not be clearer, as for me it's a regression I don't know exactly what
changes between maven 3.0.3 and 3.0.4 which can cause this problem.
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
