Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-169518501
Spell check yes.
On note 2: I agree in spirit, however I'd really like to keep accessible
very novice users. Going forward I'm going to be maintaining this article, not
my original blog post. One of the big (unsung) advantages of Zeppelin is it
makes big data products friendly to work with (e.g. copy and paste code, no
command line, no setting up an overwhelming IDE like jetbrains, etc.) Things we
tend to take for granted as developers. In my mind, for many people using this
tutorial, this is their first experience building a package from source.
My point being: Waiving my hands and saying sometimes things don't work and
its not your fault, then leaving it at that is probably a little too
dismissive, I want to let users know, "just because the build is failing- don't
get discouraged, try it again and if it still doesn't work, reach out to the
community for help, and in some cases, you just need to walk away from it for a
little while, that's life."
A blurb in there about looking through the logs is a good idea. I'm going
to disconnect my internet and try building again to get the specific error
message because in my experience (having coached a few novices through the
process), that really is the most likely reason for a failure (assuming you
have followed the directions carefully).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
