Samuel Yuan created HIVE-4289:
---------------------------------
Summary: HCatalog build fails when behind a firewall
Key: HIVE-4289
URL: https://issues.apache.org/jira/browse/HIVE-4289
Project: Hive
Issue Type: Bug
Components: Build Infrastructure, HCatalog
Affects Versions: 0.11.0
Reporter: Samuel Yuan
Assignee: Samuel Yuan
A bug in Maven makes it impossible to set a proxy for a Maven Ant POM task (see
https://jira.codehaus.org/browse/MANTTASKS-216). Building behind a firewall
results in the following error:
[artifact:pom] Downloading: org/apache/apache/11/apache-11.pom from repository
central at http://repo1.maven.org/maven2
[artifact:pom] Transferring 14K from central
[artifact:pom] [WARNING] Unable to get resource 'org.apache:apache:pom:11' from
repository central (http://repo1.maven.org/maven2): Error transferring file: No
route to host
[artifact:pom] An error has occurred while processing the Maven artifact tasks.
[artifact:pom] Diagnosis:
[artifact:pom]
[artifact:pom] Unable to initialize POM pom.xml: Cannot find parent:
org.apache:apache for project: org.apache.hcatalog:hcatalog:pom:0.11.0-SNAPSHOT
for project org.apache.hcatalog:hcatalog:pom:0.11.0-SNAPSHOT
[artifact:pom] Unable to download the artifact from any repository
Despite the error message, Ant/Maven is actually able to retrieve the POM file
by using the proxy set for Ant. However, it mysteriously fails when trying to
retrieve the checksum, which causes the entire operation to fail. Regardless, a
proxy should be set through Maven's settings.xml file. Since this is not
possible, the only way to build HCat behind a firewall right now is to manually
fetch the POM file and have Maven read it from the cache.
Ideally we would fix this in Maven, but given that this issue has been reported
for a long time in a number of separate places I think it is more practical to
modify the HCatalog build to specify the POM as a dependency, fetching it into
the cache so that the artifact:pom task can succeed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
