As background, I found that the issue is with a change to the HTTP client after Maven 2.2 timeframe that doesn't follow HTTP redirects to HTTPS. So any repos that are HTTP may generate a redirect to an HTTPS URL, and Maven poorly interprets that as a response.
See the many issues, duplicates, cross-linked issues, etc. at http://jira.codehaus.org/browse/WAGON-314 http://jira.codehaus.org/browse/MNG-4838 etc. If you can provide the segment of the console output of the build that deals with the artifact, we might be able to find out if there are changes we can make to not use (or fix the use of) the specific repos causing trouble. From Drew's original post, I'm still a proponent of removing the snapshot repos from the build. I am not sure if it would permanently solve the issue though. I'll submit a pull request for it. James Wennmacher - Unicon 480.558.2420 On 06/17/2014 01:08 PM, Joe Novalany wrote: > Not sure if this is helpful or not but here's what I found. > > My POM file located at: C:\Documents and > Settings\novalajo\.m2\repository\net\sf\ehcache\ehcache-web-parent\2.0.4\ehcache-web-parent-2.0.4.pom > > contained the following: > > <html> > <head><title>301 Moved Permanently</title></head> > <body bgcolor="white"> > <center><h1>301 Moved Permanently</h1></center> > <hr><center>nginx/1.4.1</center> > </body> > </html> > > > I found what I believe it should have contained over at: > http://svn.terracotta.org/svn/ehcache/tags/ehcache-web-2.0.4/pom.xml > > I then copied the XML from the URL above to the POM file on my machine and > then the build seem to complete successfully. > > I'm not sure where in I need to change the location so Maven knows where to > look for the correct POM file but it seems the URL has been moved which is > causing the build issues. > > Hope this helps! -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
