Michael, There are a lot of build related emails that we see in this forum. This mostly happens due to local or network firewalls preventing the connection requests from maven. Maven internally uses git and npm to build certain parts of zeppelin. Also the bower build fails at many places.
Most have been solved. Please search the online archives of this list. The archive is difficult to search, so use google site search. Use this query in google: site:mail-archives.apache.org/mod_mbox/incubator-zeppelin-users/ build error “build error” is the sample query string If you do not have the infra to build zeppelin outside a firewall then you have to build the internal targets manually. That’s how we were able to do it. Eg: You can change the git configuration to use http instead of https or other port numbers. See the git port numbers here: http://serverfault.com/questions/189070/what-firewall-ports-need-to-be-open-to-allow-access-to-external-git-repositories Regards, Prajod From: Michael Parco [mailto:[email protected]] Sent: 07 May 2015 23:14 To: [email protected] Subject: Angular Interpreter w/ HDP 2.2.4.2 Zeppelin Notebook Team, I have built the zeppelin notebook and manage it though ambari. I have had no issues with the default interpreters and I was looking to integrate the angular interpreter into my build. I have been unsuccessful in building the angular interpreter and have come across several different dependency issue along the way. Has anyone built the angular interpreter on top of a HDP stack and if so any tips/guides to do so Thanks, The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
