Comment 5 for bug 1441278

I have a change that I think will fix this issue.

From the logs, during the HDP Maven compile, maven is not finding the Jetty artifacts in the repository that we have specified in the POM file:
http://repo.hortonworks.com/content/repositories/releases/

On a successful build I see that Maven goes through various other repositories and finally finds the artifacts in:
 http://repo.hortonworks.com/content/groups/public/

On the failure build, Maven cycles through quite a few repositories and fails on people.apache.org as the connection is timing out. That is before reaching the correct repository.

I find that when I explicitly specify the ' http://repo.hortonworks.com/content/groups/public/' repository in the HDP POM file, Maven will only cycle through the two repositories that we specify when it tries to download Jetty and does not attempt to download from people.apache.org.

Example log:
Downloading: http://repo.hortonworks.com/content/repositories/releases/org/mortbay/jetty/jetty/6.1.26.hwx/jetty-6.1.26.hwx.pom
           ^MDownloading: http://repo.hortonworks.com/content/groups/public/org/mortbay/jetty/jetty/6.1.26.hwx/jetty-6.1.26.hwx.pom3/7 KB ^M7/7 KB ^M ^M
Downloaded: http://repo.hortonworks.com/content/groups/public/org/mortbay/jetty/jetty/6.1.26.hwx/jetty-6.1.26.hwx.pom (7 KB at 54.6 KB/sec)