Eclipse maven plugin getting HTTP 416 on flask fetch

I am getting this error in eclipse logs when I use maven integration plugin for eclipse in my project:

Build errors for transport-data; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources (default-resources) on project transport-data: Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources failed: Plugin org.apache.maven.plugins:maven-resources-plugin:2.4.3 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4, org.apache.maven.shared:maven-filtering:jar:1.0-beta-4, org.codehaus.plexus:plexus-interpolation:jar:1.13: Failure to transfer org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4 from was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4 from/to central ( Failed to transfer Error code 416, Requested Range Not Satisfiable

From the browser I can access the jar, but how is it that the plugin gets a 416 status response?

I am using STS 2.7.2.RELEASE (Eclipse 3.6) with Maven integration plugin on Maven 2.2.1 and my OS is Ubuntu 10.10. If someone could help me explain this mystery, I would be very grateful.



source to share

2 answers

I know this is a very old query, but I just came across it. What worked for me was removing the corresponding downloaded components in the .m2 repository. I figured there might be some partially loaded bits in there as I was using both Eclipse and command line with maven.

Hope it helps ...



HTTP 416 means the client only requested a portion of the file, but the server probably doesn't support such requests. Though I would be surprised if maven breaks its repo webserver. Another possibility is that you are behind a proxy server that does not support range requests.



All Articles