[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235562#action_235562 ] Jesse Glick commented on MNG-4428: -- Confirming that the JRE's implementation does not reliably handle

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233063#action_233063 ] Anders Hammar commented on MNG-4428: Paul, for a workaround for Cargo, see CARGO-840. I've tried

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232975#action_232975 ] Paul Davis commented on MNG-4428: - ERt, I tried the workaround and it didn't work for the codehaus

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229097#action_229097 ] Graham Leggett commented on MNG-4428: - This is a major regression that completely sinks all maven

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=214778#action_214778 ] ERt commented on MNG-4428: -- Workaround: 1. In your local repository find pom which declare inappropriate

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=212748#action_212748 ] Stephen Compall commented on MNG-4428: -- The underlying cause seems to be wagon-http-lightweight's

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209338#action_209338 ] Data Nucleus commented on MNG-4428: --- +1. Recent changes in SUN's M2 repo has broken local repos for

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=208557#action_208557 ] Kyle W. Cartmell commented on MNG-4428: --- +1 to fix ASAP - this is a huge problem as it breaks

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=208128#action_208128 ] Benjamin Jaton commented on MNG-4428: - Definitively a major issue since log4j 1.2.15 is impacted (

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205890#action_205890 ] Steve Kuo commented on MNG-4428: This should be major priority. Basically if any repository returns

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202276#action_202276 ] Paul Loy commented on MNG-4428: --- I would suggest that this is a little more important than minor. I'm